Prepare the next version iteration - #763
Merged
Merged
Conversation
Now that 3.3.0 is released, open the changelog for the next one and move the version off the released number, so a merge to main is never sitting at a version already published to RubyGems. The placeholder targets 3.3.1 and is adjusted if a feature lands before the release, which is what happened to this entry during the 3.3.0 cycle.
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.
Follow-up to the 3.3.0 release, mirroring #729.
NEXTchangelog section for v3.3.1 with the contribution placeholders.JWT::VERSION::TINYoff the released number, so main is never sitting at a version already published to RubyGems.The placeholder targets 3.3.1 and gets adjusted if a feature lands before the release, which is what happened to this entry during the 3.3.0 cycle.