ci(release-please): change PR title and ensure git tag consistency #7153
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.
Related Issue: #6988
Summary
This PR changes the
release-please
PR title tochore: release latest
. The default ischore: release master
.It also makes sure a
v
isn't added before the version in git tags. Their schema doc says it doesn't by default,but I'm not convinced (see links below) so I want to hardcode the config value. The
v
being in the tag wouldn't break anything in our CI, but Lerna doesn't add av
and we should make sure our tag format is consistent for our consumer's CI.https://github.com/googleapis/release-please/blob/bdd9b0158ce79d958da01ebf54cb6b07925bc125/schemas/config.json#L77-L79
https://github.com/googleapis/release-please/blob/bdd9b0158ce79d958da01ebf54cb6b07925bc125/src/strategies/base.ts#L139