v0.6-branch
. For a patch version, check out the stream's release branch.pom.xml
, remove -SNAPSHOT
from the <revision>
property, update versions, and commit.v
and sdk/go/v
prefixesvX.Y.Z-rc.N
and sdk/go/vX.Y.Z-rc.N
X.Y.Z
create tags vX.Y.Z
and sdk/go/vX.Y.Z
make lint-versions
.-SNAPSHOT
in pom.xml
and push.-SNAPSHOT
.env TARGET_MERGE_BRANCH=master make lint-versions
Feast vX.Y.Z
as the title.sdk/go/v tag
is required to version the Go SDK go module so that users can go get a specific tagged release of the Go SDK.-t
) to the change log generator.master
for a major/minor release, or a release branch (v0.4-branch
) for a patch release. You will need to set the branch using the --release-branch
argument.--future-release
argument. This is the version you are releasing. The version can still be changed at a later date.Breaking changes
, Implemented enhancements
, Fixed bugs
, and Merged pull requests
. Any unlabelled PRs will be found in Merged pull requests
. It's important to make sure that any breaking changes
, enhancements
, or bug fixes
are pulled up out of merged pull requests
into 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/breaking
label. 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/breaking
to PRs with undeclared breaking changes. The change log will have to be regenerated if any new labels have to be added.