chore: bump workspace version to 2.2.0 - #474
Draft
joshrotenberg wants to merge 3 commits into
Draft
Conversation
Move the workspace version from 2.0.8 past the v2.1.x git tags. Versions 2.1.0 through 2.1.3 exist only as tags on the 2.1 branch and were never published to crates.io; skipping the 2.1.x range keeps every published version number distinct from those tags.
Add changelog entries for 2.2.0 in the root crate and both macro crates, and add a README section describing how releases are published and the status of the v2.1.x git tags.
Tag and name releases of the redis-module crate v<version>, matching the v2.0.8 and v2.1.3 format that existing git dependents pin, and mark only the redis-module release as the latest GitHub release so /releases/latest points at the main crate. The other crates keep the default <crate>-v<version> tag and release names.
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.
The crates on crates.io are at 2.0.8. Git tags v2.1.0 through v2.1.3 were cut from the
2.1branch and were not published to crates.io. All changes from that branch are present onmaster.This bumps the workspace version from 2.0.8 to 2.2.0 so the next published version is ahead of the v2.1.x tags, adds the matching changelog entries, adds a README section describing how releases are published, and adds a release-plz config that tags and names redis-module releases as
v<version>, matching the existing format.Merging this triggers the existing release-plz workflow, which publishes 2.2.0 to crates.io, creates the
v2.2.0tag, and creates a GitHub release namedv2.2.0. After that, crates.io, the latest GitHub release, and the latestv-prefixed tag all point to the same version.Closes #415