mirror of
https://github.com/kubernetes-sigs/kustomize.git
synced 2026-05-21 22:41:42 +00:00
a7df00c07a
[doc]: https://github.com/golang/go/wiki/Modules#releasing-modules-v2-or-higher Per this Go modules [doc] a repo or branch that's already tagged v2 or higher should increment the major version (e.g. go to v3) when releasing their first Go module-based packages. At the moment, the kustomize repo has these top level packages in the sigs.k8s.io/kustomize module: - `cmd` - holds main program for kustomize Conceivably someone can depend on this package for integration tests. - `internal` - intentionally unreleased subpackages - `k8sdeps` - an adapter wrapping k8s dependencies This exists only for use in pre-Go-modules kustomize-into-kubectl integration and won't live much longer (as everything involved is switching to Go modules). - `pkg` - kustomize packages for export This should shrink in later versions, since the surface area is too large, containing sub-packages that should be in 'internal'. - `plugin` - holds main programs for plugins This PR changes the top level go.mod file from ``` module sigs.k8s.io/kustomize ``` to ``` module sigs.k8s.io/kustomize/v3 ``` and adjusts all import statements to reflect the change.
Scripts and configuration files for publishing a
kustomize release on the releases page.
Build a release locally
Install cloud-build-local, then run
./build/localbuild.sh
to build artifacts under ./dist.
Publish a Release
Get on an up-to-date master branch:
git checkout master
git fetch upstream
git rebase upstream/master
Define the version (see semver principles), e.g.:
version=v1.0.3
Tag the repo:
git tag -a $version -m "$version release"
Push the tag upstream:
git push upstream $version
The new tag will trigger a job in Google Cloud Build to put a new release on the releases page.