Repository navigation

releases

Public

About

Toolset for automating Submariner releases.

17 stars

11 watching

Name		Name	Last commit message	Last commit date
.github		.github
releases		releases
scripts		scripts
.dockerignore		.dockerignore
.gitignore		.gitignore
.krew.yaml		.krew.yaml
.markdownlinkcheck.json		.markdownlinkcheck.json
.markdownlint.yml		.markdownlint.yml
.shellcheckrc		.shellcheckrc
.shipyard.e2e.yml		.shipyard.e2e.yml
.yamllint.yml		.yamllint.yml
CODE-OF-CONDUCT.md		CODE-OF-CONDUCT.md
CODEOWNERS		CODEOWNERS
CODEOWNERS.in		CODEOWNERS.in
CONTRIBUTING.md		CONTRIBUTING.md
Dockerfile.dapper		Dockerfile.dapper
LICENSE		LICENSE
Makefile		Makefile
README.md		README.md

Repository files navigation

Releases

To create or advance a release, simply run make release VERSION='$semver', e.g.

`make release VERSION='1.2.3'
`make release VERSION='1.2.3-rc1'

To run the process without making external changes (GitHub, Quay...), run the command with DRY_RUN=true.

Make sure you set the GITHUB_TOKEN environment variable to a Personal Access Token which has at least public_repo access to your repository.

By default, the action will try to push to the GitHub account used in the origin remote. If you want to use a specific GitHub account, set GITHUB_ACTOR to the desired account, e.g.