Repository navigation
Merge release 3.0.0 back into master and start 3.0.1-SNAPSHOT - #313
Merged
Merged
Conversation
|
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Release Finish run 38737416874 tagged `v3.0.0` and published it to Maven Central, but its last two steps could not push to `master` because of branch protection (`GH006: Changes must be made through a pull request`). This PR does those steps:
Merge with a merge commit (not squash or rebase) so that the tagged commit 258767c ends up in master's history, as it did for 2.0.16.
After merging, `release/3.0.0` can be deleted (the workflow's last step was skipped).