upgrading-golang
Comprehensive automation for upgrading Go versions across source code, Docker images, and CI/CD pipelines.
Install
mkdir -p .claude/skills/upgrading-golang && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/2473" && unzip -o skill.zip -d .claude/skills/upgrading-golang && rm skill.zipInstalls to .claude/skills/upgrading-golang
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Upgrades Go version across the entire Chainloop codebase including source files, Docker images, CI/CD workflows, and documentation. Use when the user mentions upgrading Go, golang version, or updating Go compiler version.Key capabilities
- →Update go.mod files with new Go versions
- →Reconcile Docker image SHA256 digests
- →Update project documentation in CLAUDE.md
- →Update Atlas migration Docker images
- →Sync Atlas CLI versions in common.mk
How it works
The tool performs a multi-step update by pulling official Docker images to extract SHA256 digests, then applying these versions and hashes across specific project configuration files and documentation.
Inputs & outputs
When to use upgrading-golang
- →Update Go version in project configuration
- →Sync Docker images with new Go compiler
- →Refresh documentation with new language version
About this skill
Upgrading Golang Version
This skill automates the comprehensive Go version upgrade process across all components of the Chainloop project.
Process
1. Confirm Target Versions
Ask the user:
- What Go version they want to upgrade to (e.g., "1.25.3")
- Whether they also want to upgrade Atlas migrations Docker image (if yes, ask for target Atlas version, e.g., "0.38.0")
2. Get Docker Image Digest
Pull the official golang Docker image and extract its SHA256 digest:
docker pull golang:X.XX.X
Extract the SHA256 digest from the output (format: sha256:abc123...).
3. Update Source Code
Update the go directive in:
./go.mod
IMPORTANT: Do NOT update ./extras/dagger/go.mod per project policy.
Pattern to replace:
go X.XX.X
4. Update Docker Images
Update all Dockerfiles with the new version and SHA256 digest. See files-to-update.md for the complete list.
Pattern to replace:
FROM golang:X.XX.X@sha256:OLD_DIGEST AS builder
With:
FROM golang:X.XX.X@sha256:NEW_DIGEST AS builder
5. Update Documentation
Update the version reference in ./CLAUDE.md under "Key Technologies":
- **Language**: Go X.XX.X. To know how to upgrade go version, see docs/runbooks
6. Update Atlas Docker Image and CLI (Optional)
If the user requested an Atlas upgrade:
6a. Pull the Atlas Docker image and extract its SHA256 digest:
docker pull arigaio/atlas:X.XX.X
Extract the SHA256 digest from the output (format: sha256:abc123...).
6b. Update ./app/controlplane/Dockerfile.migrations:
Pattern to replace:
# from: arigaio/atlas:X.XX.X
# docker run arigaio/atlas@sha256:OLD_DIGEST version
# atlas version vX.XX.X
FROM arigaio/atlas@sha256:OLD_DIGEST as base
With:
# from: arigaio/atlas:X.XX.X
# docker run arigaio/atlas@sha256:NEW_DIGEST version
# atlas version vX.XX.X
FROM arigaio/atlas@sha256:NEW_DIGEST as base
7c. Update ./common.mk for make init:
IMPORTANT: Before updating the version in common.mk, ALWAYS test that the Atlas version is available via the curl command:
curl -sSf https://atlasgo.sh | ATLAS_VERSION=vX.XX.X sh -s -- --version
If the command fails or the version is not available, do NOT update common.mk. Only the Docker image should be updated in this case.
Update the Atlas CLI installation version in the init target:
Pattern to replace:
curl -sSf https://atlasgo.sh | ATLAS_VERSION=vX.XX.X sh -s -- -y
With the new version (note: use v prefix for the version):
curl -sSf https://atlasgo.sh | ATLAS_VERSION=vX.XX.X sh -s -- -y
7. Verify Changes
Run verification commands:
make test
make lint
If errors occur, address them before completing the upgrade.
8. Final Checks
- Ensure all license headers are updated (2024 → 2024-2025 or add current year)
- Run
buf format -wif any proto files were affected - Run
wire ./...if any constructor dependencies changed - Verify
go.modchanges withgo mod tidy
Important Notes
- Always use SHA256 digests for Docker images for security and reproducibility
- The dagger module (
./extras/dagger/go.mod) must NOT be updated - Test thoroughly as Go upgrades can introduce breaking changes
- Multiple components use Go: CLI, Control Plane, and Artifact CAS
When not to use it
- →Updating the dagger module go.mod file
- →Updating Atlas versions without verifying availability via curl
Prerequisites
Limitations
- →Requires manual confirmation of Atlas version availability
- →Does not update the dagger module
How it compares
This tool automates the synchronization of Go versions across multiple project components and documentation, ensuring consistent digests and avoiding manual file editing.
Compared to similar skills
upgrading-golang side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| upgrading-golang (this skill) | 1 | 5mo | Review | Intermediate |
| update-go-version | 1 | 6mo | Review | Beginner |
| upgrade-deps | 0 | 2mo | No flags | Advanced |
| bazel-build-optimization | 14 | 2mo | No flags | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by chainloop-dev
View all by chainloop-dev →You might also like
update-go-version
grafana
Update Go version across the Tempo codebase (go.mod, tools/go.mod, Dockerfile, CI workflows, tools image tag)
upgrade-deps
obot-platform
Upgrade dependencies and runtimes safely, run CI, and report higher-risk options.
bazel-build-optimization
wshobson
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.
linux-production-shell-scripts
davila7
This skill should be used when the user asks to "create bash scripts", "automate Linux tasks", "monitor system resources", "backup files", "manage users", or "write production shell scripts". It provides ready-to-use shell script templates for system administration.
machine-learning-ops-ml-pipeline
sickn33
Design and implement a complete ML pipeline for: $ARGUMENTS
windows-builder
hashicorp
Build Windows images with Packer using WinRM communicator and PowerShell provisioners. Use when creating Windows AMIs, Azure images, or VMware templates.