Automatic development releases are removed #787
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Every GitHub release, including pre-releases, will notify any repository watchers. We were previously creating a new development release on every commit to
main
. This creates a lot of noise for anyone watching the repository. Many of these commits aren't meaningful enough to warrant creating a development release.The reason we did this was so we could run the cross-version tests using the latest changes in main in the form of a distribution. We feel we've outgrown this need and are removing the automated development releases.
Instead,
main
will be tested by building from source and development releases will no longer be created on every commit. There will still be a way to create development releases manually for changes that are meaningful enough and need to be used before a proper release.Closes #780