Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions Makefile
Original file line number Diff line number Diff line change
Expand Up @@ -24,6 +24,10 @@ build:
release:
go run github.com/goreleaser/goreleaser/v2@$(GORELEASER_VERSION) release --clean

.PHONY: release-skip-docker
release-skip-docker:
go run github.com/goreleaser/goreleaser/v2@$(GORELEASER_VERSION) release --clean --skip=docker

.PHONY: release-notes
release-notes:
@./.ci/release-github.sh
Expand Down
17 changes: 17 additions & 0 deletions RELEASE.md
Original file line number Diff line number Diff line change
Expand Up @@ -26,3 +26,20 @@ Tag the release via your preferred tagging method. Tagging a release (v1.1.0) v

This will trigger a build in the CI that will create the Build Artifacts
and a Release in the Github UI.

### Testing release locally

> [!TIP]
> Configure your AWS credentials using https://github.com/okta/okta-aws-cli
> Use gh cli to configure the GITHUB_TOKEN

1. export GORELEASER_CURRENT_TAG=v0.0.99999
2. export GITHUB_TOKEN=$(gh auth token)
3. git tag "${GORELEASER_CURRENT_TAG}" -f
3. make release-skip-docker

#### Further details

What does `GORELEASER_CURRENT_TAG` mean?

See https://goreleaser.com/cookbooks/set-a-custom-git-tag