-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Race condition when creating GitHub releases #2799
Comments
I just ran into this myself (I think)? I installed some modules and saw a warning that |
@petetnt - That's not related, Homebrew is updated separately by the Homebrew community.
This is related, the GitHub release sometimes incorrectly says it's a prerelease.
This is the development version. Builds from master (such as nightly builds) will have |
@Daniel15 Yeah, the Homebrew part was more of back story (as was the |
The release scripts for Yarn create a new GitHub release.
yarn/circle.yml
Line 52 in 4081529
This results in a race condition like this:
This is very confusing: Sometimes builds that are prereleases are marked as stable (eg. see Homebrew/homebrew-core#10147), while other times stable releases are marked as prereleases (eg. see nodejs/docker-node#337 (comment)).
The correct behaviour should be as follows:
For example, if we're publishing 0.23.2 and the latest stable is 0.23.1, it should be marked as stable. On the other hand, if we're publishing 0.24.0 and the latest stable is 0.23.1, it should not be marked as stable.
To simplify things, I might also unify the Windows and Linux builds so they upload the build artifacts in the same way, and also automatically bump the version numbers on the site.
The text was updated successfully, but these errors were encountered: