v3.4.20

Release 3.4.20

v3.4.17

Release 3.4.17

v3.4.16

Release 3.4.16

v3.4.15

Release 3.4.15

v2.1.2

At log in, if the user has entries in their repository cache, do not perform a refresh. Only run the refresh when the cache is empty. Users can choose to perform a refresh on the My Roles page.

This reduces load on the Celery processes, and gives the user some control over how frequently requests are sent to the GitHub API. There are users with access to over 2,000 GitHub repositories, and Galaxy makes 2 requests per repo in an attempt to determine which repos contain roles. The GitHub API rate limits users to 5,000 requests per hour, so it doesn't take much to exceed the limit.

v2.1.1

• Refresh role counts task now identifies roles where the combination of github_user/github_repo no longer exists in GitHub and removes the role.
• Refresh role counts task now recognizes when a role's github_user/github_repo has changed in GitHub and updates the role.
• The refresh roles task that runs when the user logs in or clicks the refresh button now recognizes when a role's github_user/github_repo has changed in GitHub and updates the role.
• The delete process in the UI now traps a failed Delete request, and notifies the user to click the refresh button to update the list of roles.
• The My Roles page no longer displays both an enabled and disabled refresh button simultaneously when the refresh task completes.

v2.1.0

• Added role_type property to roles
• Added support for Container Enabled and Container App role types
• Use GitHub HTML for README
• Made 'EL' platform searchable again