-
Notifications
You must be signed in to change notification settings - Fork 32
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
Release inconsistency #437
Comments
It would not be proper to not set this as the latest release, because it's definitely the latest release and an emergency security one. So setting it as pre-release would not send the right message. I can see more options moving forward:
What do you think? |
Thanks for the response. That's a good point. In that case, I think the ideal solution would be to make it a full release instead for all platforms, with all artifacts included. With that, you could either bump all platform versions to With regards to another channel, do you have a recommendation? Is there a json feed available? We would really prefer not to try and scrape the website for the latest release info but that's the only other place we are currently aware of. I also noticed the website still lists Thanks |
For our own website, we are actually using a We have platform specific (in the meantime, everything will go back to normal with 14.0.9 planned for next week.) |
Does this feature already exist in Firefox Stable?
I'm not sure
Does this feature already exist in Firefox ESR?
I don't know
Feature description
Hi,
We use automation to grab the latest version and artifacts from Github releases here. Unfortunately the latest release 14.0.8 breaks our automation as it is an OS specific partial release and is missing linux artifacts.
Could you please consider marking partial or OS specific releases not as
latest
on Github? They could be marked as prerelease. That way downstream automation will not treat it as the latest full/proper release.Thanks
Alternatives considered
We would have to update our ci to allow us to manually ignore releases, which defeats the purpose of automation
Is this related to a problem?
The
latest
marked release on Github should ideally be a full/proper release.The text was updated successfully, but these errors were encountered: