-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Addons: version last build date #11308
Labels
Needed: design decision
A core team decision is required
Comments
The problem I see with either of the approaches listed here is that the endpoint wouldn't be able to be cached anymore. A build on any version will clear the cache for all the versions. |
Mmm good point. This does feel like a helpful feature for showing how fresh a version is, but not important enough to incur cache invalidation yet. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Raising this from a support request as a discussion for a potential API change on the addons. The use case here is showing the most recently built versions in the version data for a custom version menu or in the flyout. There are maybe two ways to approach this:
I feel like the sorting could be optional and we will want to have the last build date on the version instances either way. The sorting mechanism will be prone to randomizing the version list for projects that have to go back and edit a release for any reason.
Front conversations
The text was updated successfully, but these errors were encountered: