smithery.ai

upgrading-golang

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.

First seen Mar 20, 2026

Installation

$ npx skills add https://smithery.ai

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Skill metadata

Parsed from SKILL.md frontmatter.

Declared agents claude-code

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 3,687 B
  • docs SUMMARY.md 245 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

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:

  1. What Go version they want to upgrade to (e.g., "1.25.3")
  2. 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](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 -w if any proto files were affected
  • Run wire ./... if any constructor dependencies changed
  • Verify go.mod changes with go 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