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.
Security Assessment
About upgrading-golang
The 'upgrading-golang' skill automates the process of upgrading the Go version across the entire Chainloop codebase. This includes the Go source files, Docker images, CI/CD workflows, and documentation. It solves the problem of manual, error-prone version upgrades, ensuring consistency and security across all components. This skill helps developers ensure that their projects are using the latest Go version with minimal effort, preventing any compatibility issues and ensuring that the entire ecosystem remains up to date with the latest Go features and fixes.
FAQ
How do I use the upgrading-golang skill?
To use this skill, simply provide the desired Go version and optionally the Atlas version if you wish to update the Atlas Docker image. The skill will guide you through each step, including pulling Docker images, updating source code, modifying Dockerfiles and workflows, and updating documentation.
Is this skill compatible with all versions of Go?
Yes, the skill supports upgrading to any specific Go version. However, you must test for breaking changes in the codebase, as Go version upgrades may introduce compatibility issues or deprecate certain features.
What are the main limitations or requirements of this skill?
The skill requires you to update Docker images and workflows for all affected components. The dagger module ('./extras/dagger/go.mod') must not be updated as per project policy. You should also verify that the Atlas version is available before updating the version in 'common.mk'. Thorough testing is essential before completing the upgrade.
What happens if an Atlas upgrade fails?
If the Atlas version is unavailable or the curl command fails, the Atlas Docker image should still be updated, but the version in 'common.mk' should not be changed. The upgrade process will need to be adjusted accordingly.
What verification steps are involved in this process?
The skill provides a set of verification steps including running 'make test' and 'make lint'. Additionally, you need to ensure all license headers are updated, and run necessary format and dependency commands like 'buf format -w' and 'wire ./...' if applicable.
Install upgrading-golang
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
chainloop-dev/chainloop