Skip to content

versions: github-release keeps an image's variant; golangci-lint at v2.15.0-alpine - #119

Merged
aledbf merged 1 commit into
mainfrom
versions-image-tag-suffix
Nov 18, 2026
Merged

aledbf merged 1 commit into
mainfrom
versions-image-tag-suffix

Conversation

@aledbf

@aledbf aledbf commented Nov 18, 2026

Copy link
Copy Markdown
Member

The first step toward golangci-lint as golangci/golangci-lint:v2.15.0-alpine in every repository that runs the image (go-tools, devcontainer-cli, shipset, spin-ami).

Why the track changes first. Under github-release, the newest is the release tag, v2.15.0. An image pinned at v2.15.0-alpine was therefore behind for ever, and a refresh would move it back to v2.15.0 with the digest of the image without the variant. releaseVersion now keeps an image's variant, meaning what its tag says after the version: v2.15.0-alpine moves to v2.16.0-alpine. That is what the go track already does for 1.27.4-trixie. A download's version keeps nothing, and the format has no new field.

go-tools' own entry is at v2.15.0-alpine, pinned by versions bump (sha256:2ba875b9…). versions check reports it as current.

Checked: task test, task lint (it ran on the alpine image: 0 issues, every gate OK), task site, and task mutate (12 refused, 0 survived). The other three repositories follow once this is released: each takes the new go-tools version and moves its entry.

🤖 Generated with Claude Code

…is the -alpine image

An image pinned at v2.15.0-alpine was behind for ever under github-release, whose newest is the
release, v2.15.0, and a refresh moved it to the image without the variant. The track now spells
the newest as the pin does, as go does for 1.27.4-trixie.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@aledbf
aledbf force-pushed the versions-image-tag-suffix branch from eac6dfb to 60849a1 Compare November 18, 2026 20:47
@aledbf
aledbf merged commit 987a8c1 into main Nov 18, 2026
3 checks passed
@aledbf
aledbf deleted the versions-image-tag-suffix branch November 18, 2026 20:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant