mikku
is a CLI tool to help version management and Kubernetes manifest updates.
- Create GitHub releases with bumping Semantic Versioning tag
If you use Windows or Linux, replace windows_amd64
or linux_amd64
instead of darwin_amd64
.
$ VERSION=1.0.1
$ curl -O -L https://github.com/p1ass/mikku/releases/download/v${VERSION}/mikku_${VERSION}_darwin_amd64.tar.gz
$ tar -zxvf mikku_${VERSION}_darwin_amd64.tar.gz
$ chmod a+x mikku
$ mv mikku /usr/local/bin/mikku
$ mikku --help
Binaries are available on GitHub releases. p1ass/mikku/releases
$ go install github.com/p1ass/mikku/cmd/[email protected]
$ mikku --help
You need an OAuth2 access token. Generate personal API token with repo scope.
MIKKU_GITHUB_ACCESS_TOKEN
: your OAuth2 access token.MIKKU_GITHUB_OWNER
: repository owner or org name.- Ex.
p1ass
whenp1ass/mikku
- Ex.
$ export MIKKU_GITHUB_ACCESS_TOKEN=[YOUR_ACCESS_TOKEN]
$ export MIKKU_GITHUB_OWNER=[GITHUB_OWNER_NAME]
When the latest tag name is v1.2.3
, the below command bump to v1.2.4
.
$ mikku release sample-repository patch
Note that mikku
doesn't build and push a docker image, so you have to do it using CI service such as CircleCI.
$ mikku release sample-repository v1.0.0
Create a tag and a GitHub release.
If you use major
, minor
, or patch
, the latest tag name must be compatible with Semantic Versioning.
major
: major version upminor
: minor version uppath
: patch version upversion
: create tag with a given version. Ex.v1.0.0
$ mikku release sample-repository v1.0.0
$ mikku release sample-repository patch # v1.0.0 → v1.0.1
$ mikku release sample-repository minor # v1.0.1 → v1.1.0
$ mikku release sample-repository major # v1.1.0 → v2.0.0
$ go build -o mikku cmd/mikku/main.go
go test -v ./...
MIT