docs: add package port bumps to the release steps - #71
Merged
Merged
Conversation
Without this step a release leaves vcpkg, and later ConanCenter, on the previous version.
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
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.
CONTRIBUTING's release steps stopped at pushing the tag, so a release would leave the vcpkg port on the old version. Step 4 now covers the follow-up PRs: vcpkg now, and ConanCenter once conan-io/conan-center-index#31050 merges.
Testing
curl ... | shasumcommand reproduces the SHA512 in vcpkg's 0.6.2 portfile and the sha256 in the Conan recipe's conandata.x-add-version. The git-tree it recorded matched the working tree, so the step skips a commit-then-amend dance.make lint,make test,./tools/test_consumers.sh, andmake docs.