v0.6-branch. For a patch version, check out the stream's release branch.
<revision>property, update versions, and commit.
env TARGET_MERGE_BRANCH=master make lint-versions
sdk/go/v tagis required to version the Go SDK go module so that users can go get a specific tagged release of the Go SDK.
masterfor a major/minor release, or a release branch (
v0.4-branch) for a patch release. You will need to set the branch using the
--future-releaseargument. This is the version you are releasing. The version can still be changed at a later date.
Fixed bugs, and
Merged pull requests. Any unlabelled PRs will be found in
Merged pull requests. It's important to make sure that any
bug fixesare pulled up out of
merged pull requestsinto the correct category. Housekeeping, tech debt clearing, infra changes, or refactoring do not count as
enhancements. Only enhancements a user benefits from should be listed in that category.
compat/breakinglabel. However, it's important to double check each PR's release notes and contents for changes that will break API compatibility and manually label
compat/breakingto PRs with undeclared breaking changes. The change log will have to be regenerated if any new labels have to be added.