Repository navigation
feat: port action from Node to Go and decouple image tags - #312
Merged
Merged
Conversation
marcusramberg
force-pushed
the
marcus/go_port
branch
from
October 23, 2026 07:40
717b534 to
872c052
Compare
nikolaik
reviewed
Oct 23, 2026
| @@ -0,0 +1,48 @@ | |||
| name: release | |||
|
|
|||
| # When a release is published for a semver tag (vX.Y.Z), move the matching | |||
There was a problem hiding this comment.
I think we should drop the mutable tags completely. I've seen many do the same recently.
Author
There was a problem hiding this comment.
Well, I'm working towards trying to make releasing this less of a pain, and doing that works against that. :-/
marcusramberg
force-pushed
the
marcus/go_port
branch
from
October 23, 2026 09:40
872c052 to
a154223
Compare
Rewrite the manager in Go (same env-var contract and container interface):
- internal/config, set, googlews, githuborg, app packages with unit tests
- multi-stage Dockerfile producing a distroless static binary
- CI switched to Go build/test; CodeQL to go; Renovate npm -> gomod
- remove all Node sources, tests and tooling
Fix the image-tag release pain: action.yml now pulls
ghcr.io/remarkable/githubusermanager:${{ github.action_ref }} and CI tags the
image to match the refs callers use (main, vX.Y.Z, vX.Y, vX, sha). No hardcoded
version to bump before a release. Also unifies the registry on ghcr.io.
Add release workflow that moves the major/minor git tags (vX, vX.Y) to each
published vX.Y.Z release so @v1 style references resolve to the latest release.
marcusramberg
force-pushed
the
marcus/go_port
branch
from
October 23, 2026 09:45
a154223 to
29797b5
Compare
marcusramberg
marked this pull request as ready for review
October 23, 2026 10:16
…tly and have immutable version tags
marcusramberg
force-pushed
the
marcus/go_port
branch
from
October 23, 2026 13:17
3098779 to
74b66bc
Compare
nikolaik
approved these changes
Oct 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is a 1-to-1 rewrite to go, no new features in this round
Rewrite the manager in Go (same env-var contract and container interface):
Fix the image-tag release pain: action.yml now pulls
ghcr.io/remarkable/githubusermanager:${{ github.action_ref }} and CI tags the
image to match the refs callers use (main, vX.Y.Z, vX.Y, vX, sha). No hardcoded
version to bump before a release. Also unifies the registry on ghcr.io.
Add release workflow that moves the major/minor git tags (vX, vX.Y) to each
published vX.Y.Z release so @v1 style references resolve to the latest release.
Marking this as draft as I'm still verifying the details