Repository navigation
chore: bump dependencies, tooling, CI actions and base image - #20
Merged
Merged
Conversation
- x/tools v0.49.0 -> v0.50.0, x/mod v0.40.0 -> v0.41.0, x/sync v0.22.0 -> v0.23.0 (plugin-module-register already latest) - golangci-lint v2.13.1 -> v2.13.2 (Dockerfile + .custom-gcl.yml) - Docker base image bookworm -> trixie (Debian 13) for both stages - CI actions: metadata-action v5 -> v6, setup-buildx-action v3 -> v4, login-action v3 -> v4, build-push-action v5 -> v7. Each major is a Node 24 runtime + ESM rewrite; none of the removed inputs/outputs are used by this workflow. Verified locally: go build/vet/test pass, custom-gcl builds against v2.13.2 and reports 0 issues, and the full image builds on trixie with all shipped binaries running. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.
Bumps everything that was behind.
Go dependencies
golang.org/x/toolsv0.49.0 → v0.50.0golang.org/x/modv0.40.0 → v0.41.0 (indirect)golang.org/x/syncv0.22.0 → v0.23.0 (indirect)github.com/golangci/plugin-module-registerunchanged — v0.1.2 is already latestTooling
src/Dockerfileandsrc/.custom-gcl.yml(these two must stay in lockstep)Base image
golang:1.27-bookworm→golang:1.27-trixie(Debian 13) for both build and final stagesCI actions
All four were a major behind:
docker/metadata-actionv5 → v6docker/setup-buildx-actionv3 → v4docker/login-actionv3 → v4docker/build-push-actionv5 → v7Each of those majors is a Node 24 runtime + ESM rewrite. I read the release notes; none of the removed inputs/outputs are used by this workflow, so they're drop-in.
Verification
Run locally, not just eyeballed:
go build ./...,go vet ./...,go test ./...— all pass (4 test packages)golangci-lint custom -vto rebuild the plugin binary against it, then./custom-gcl run→ 0 issuesNote: Go itself is already current — go1.27.1 is the newest release and the
1.27image tag tracks it.🤖 Generated with Claude Code