-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
docs(all): update release instructions #3107
Conversation
RELEASING.md
Outdated
automatically opened with a title like "chore: release 0.XX.0", where XX is the | ||
next version to be released. To cut a release approve and merge this pull | ||
request. Doing so will update the `CHANGES.md`, tag the merged commit with the | ||
appropriate version , and draft a GitHub release. |
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.
Draft? Does the person doing the release need to do anything?
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.
I think the is the terminology used for releases. The button in Github to do this is Draft a release
. And nope, it is done automagically. Here is an example of an automated github release: https://github.com/googleapis/google-cloud-go/releases/tag/v0.70.0
RELEASING.md
Outdated
|
||
### Automated Release | ||
|
||
If there are changes that have not yet been released a pull request should be |
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.
Specify a PR from release-please? Link to those docs?
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.
Looks like this change wasn't uploaded?
Co-authored-by: Tyler Bui-Palsulich <26876514+tbpg@users.noreply.github.com>
RELEASING.md
Outdated
automatically opened with a title like "chore: release 0.XX.0", where XX is the | ||
next version to be released. To cut a release, approve and merge this pull | ||
request. Doing so will update the `CHANGES.md`, tag the merged commit with the | ||
appropriate version , and draft a GitHub release. |
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.
appropriate version , and draft a GitHub release. | |
appropriate version, and draft a GitHub release. |
RELEASING.md
Outdated
|
||
### Automated Release | ||
|
||
If there are changes that have not yet been released a pull request should be |
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.
Looks like this change wasn't uploaded?
They are live now, turns out it helps if you |
No description provided.