Browse / Deployment Devops / Update Package Version

Update Package Version

Updates Nix package versions and corresponding SHA256 checksums from new release manifests.

SkillDeployment DevopsRelease

The source repository doesn't declare a license. Check its terms before reusing the code.

Key features

  • Extracts platform-specific SHA256 checksums from manifest files
  • Validates version numbers, checksum formats, and file existence
  • Updates both the central versions.json and package-specific .nix files
  • Provides clear error handling for failed updates
  • Fetches release manifests from a provided URL

Use cases

  • Updating a dependency in a Nix project to its latest release.
  • Automating package maintenance for a personal or team Nix overlay.
  • Ensuring Nix package definitions are synchronized with new software releases.

FAQ

How does this skill improve my workflow?

It significantly speeds up dependency management and reduces the chance of manual errors. Instead of manually finding checksums and editing multiple files, you can update a package with a single, clear instruction to Claude.

When should I use this skill?

Use this skill whenever a new version of a Nix package you manage is released. It's specifically designed for projects that use a central `versions.json` file and individual package `.nix` files for defining dependencies.

What capabilities does it provide?

This skill can fetch release manifests from URLs, parse them to extract SHA256 checksums for multiple platforms (Linux/macOS on x86_64/aarch64), and intelligently update both `versions.json` and the correct `.nix` file with the new data.

What does the Update Package Version skill do?

This skill automates the entire process of updating a Nix package's version number and its corresponding platform-specific SHA256 checksums. It fetches data from a release manifest and applies the changes to your local configuration files.