Preparing 0.41.0 release #3620
Merged
Preparing 0.41.0 release #3620
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
It seems OK for rules_go to depend on a future release of Gazelle, but not OK for Gazelle to depend on a future release of rules_go. So we should release rules_go first |
fmeum
approved these changes
Jul 10, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Updating version strings for 0.41.0 release. For this release, I intentionally avoid upgrading dependencies, because we just updated them 2 weeks ago and it might bring additional disruption to an already disruptive release.
This release requires next release of Gazelle; and next release of Gazelle requires this release. @fmeum How to release new versions of two Bazel modules that depends on each other at the same time?