-
Notifications
You must be signed in to change notification settings - Fork 3.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: prepare 3.0.0 release candidate again #12379
Conversation
Release-As: 3.0.0-rc.1
.release-please-manifest.json
Outdated
@@ -1,3 +1,3 @@ | |||
{ | |||
".": "2.9.6" | |||
".": "2.9.6-rc.1" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this still be 2.9.6?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes it should be 2.9.6
, not sure about the -rc.1
yet though. the Release-As: 3.0.0-rc.1
comment in the commit body was not being detected as it is supposed to be. This is probably a bug in release-please
, but given time constraints I'm opting to run a new release pipeline with a versioning strategy of always-bump-major
.
Release-As: 3.0.0-rc.1
What this PR does / why we need it:
The existing minor release is not picking up our custom version via the
Release-As
commit. Before debuggingrelease-please
to figure out way, I'm hoping this will force the correct version.