Skip to content

Restart the release history at v0.1.0 #34

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
imanimanyara merged 1 commit into from
Nov 14, 2026
Merged

Restart the release history at v0.1.0 #34

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
26 changes: 11 additions & 15 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,24 +5,20 @@ and callers pin `go-release.yml@<commit> # vX.Y.Z`.

## [Unreleased]

## [1.0.1] - 2026-11-14
## [0.1.0] - 2026-11-14

### Fixed

- `go-release.yml` sets `GOPRIVATE` and `GONOSUMDB` to every Simtabi-owned org, not only the
caller's, so a release fetches our own modules from git and never through proxy.golang.org.
`sangehq/authama`'s release pulled `github.com/simtabi/go-notifykit/src` through the public proxy
(finding R-INC-13). `go-release/tests/` pins the list.

## [1.0.0] - 2026-11-13

First tagged release of the shared workflows.
First tagged release of the shared workflows. It replaces `v1.0.0` and `v1.0.1`, withdrawn on
2026-11-14 in a planned history reset; a caller pinned to either moves to this version.

- `.github/workflows/go-release.yml`: the reusable Go release pipeline every Go project's
`release.yml` calls. It publishes on the repository's GitHub release only, on a pushed `vX.Y.Z` tag
or on request.
or on request. Inputs: `tag`, `goreleaser-config`, `go-version-file`, `module-alias-prefix`,
`changelog`, `post-release`, `runs-on`, `environment`, `node-version` (default: latest), and the
optional `SIGNPATH_API_TOKEN` secret.
- The release job sets `GOPRIVATE` and `GONOSUMDB` to every Simtabi-owned org, so a release fetches
our own modules from git and never through proxy.golang.org (finding R-INC-13 from the
`sangehq/authama` review). `go-release/tests/` pins the list.
- `templates/go/release.yml`: the caller to copy.

[Unreleased]: https://github.com/simtabi/.github/compare/v1.0.1...HEAD
[1.0.1]: https://github.com/simtabi/.github/compare/v1.0.0...v1.0.1
[1.0.0]: https://github.com/simtabi/.github/releases/tag/v1.0.0
[Unreleased]: https://github.com/simtabi/.github/compare/v0.1.0...HEAD
[0.1.0]: https://github.com/simtabi/.github/releases/tag/v0.1.0
5 changes: 3 additions & 2 deletions go-release/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,8 +17,9 @@ Push a version tag only for final code: tags are final, and a pushed tag publish

## Versions

This repository tags each change to the shared workflow as a release (`v1.0.0` on 2026-11-13 is the
first), and tags are final: a fix gets the next version. A caller pins
This repository tags each change to the shared workflow as a release (`v0.1.0` on 2026-11-14 is the
first; an earlier `v1.0.0` and `v1.0.1` were withdrawn in a planned history reset), and tags are
final: a fix gets the next version. A caller pins
the tag's commit with a `# vX.Y.Z` comment, which is the form Dependabot's github-actions updater
recognises: it opens a pull request moving the commit and the comment together when a new tag appears.
A pin to a bare commit, or a comment that names a pull request, is never updated by Dependabot.
Expand Down
Loading