ci: set initial version to v0.51.1 #6810
Merged
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.
Description
The release PR shows many commits already included in previous versions. I guess it's because the latest version defined in
.release-please-manifest.json
is v0.51.4, which is not in the main branch, and Release Please doesn't find it. My somewhat incomplete understanding is that Release Please goes back through the commits until it finds the v0.51.4 commit and, as a result, the release PR includes commits that have already been released.If my understanding above is correct, the problem should be solved by specifying the tags present in the main commit, so this PR changes the latest version to v0.51.1.
Related PRs
Checklist