Lockfile & Nix Hashes

Name: Lockfile & Nix Hashes
Author: Cosmian

Keep Nix vendor hashes in sync when Cargo.lock or pnpm-lock.yaml changes

by Cosmian(0) 0 installs

Free

Free account. Installing gives you the manifest plus copy-paste snippets.

See reviews

About

Instruction file imported from Cosmian/kms (.github/instructions/lockfile-hashes.instructions.md). Copyright stays with the author.

Lockfile → Nix vendor hash sync

When a lock file changes, the Nix vendor hashes must be updated to match.

Checklist

Update nix/expected-hashes/ files with the correct sha256-... hash from CI output
Hash files: server.vendor.{static,dynamic}.sha256, cli.vendor.{static,dynamic}.{darwin,linux}.sha256, ui.vendor.{fips,non-fips}.sha256, ui.pnpm.{darwin,linux}.sha256

When CI reports a hash mismatch, first verify the lock file changed intentionally in this PR; if not, revert it.

Rule 4.11 of /kms-sync-rules. For the full Nix workflow, see nix.instructions.md.

Use it

Copy one of these into your project. Installing also returns the manifest and these snippets.

# after Install: the listing is in your workspace's routing pool - a plan picks it for its slot
curl -s -X POST https://api.opensmartroute.ai/api/v1/route -H 'Authorization: Bearer $OSR_API_KEY' -H 'Content-Type: application/json' -d '{"text": "...", "plan": true}'

Manifest

An Open Capability Manifest: the router reads it to know what this does, what it costs and when to pick it.

cosmian-kms-lockfile-hashes-instructions.ocm.jsonjson

{
  "ocm": "1",
  "id": "cosmian-kms-lockfile-hashes-instructions",
  "kind": "skill",
  "name": "Lockfile & Nix Hashes",
  "description": "Keep Nix vendor hashes in sync when Cargo.lock or pnpm-lock.yaml changes",
  "publisher": "Cosmian",
  "version": "1.0.0",
  "capabilities": {
    "domains": [
      "general"
    ],
    "tags": [
      "skill-md",
      "github-instructions"
    ],
    "languages": [
      "en"
    ]
  },
  "quality_prior": 0.6,
  "examples": [
    "Keep Nix vendor hashes in sync when Cargo.lock or pnpm-lock.yaml changes"
  ],
  "primary": false,
  "metadata": {
    "source": {
      "provider": "github-instructions",
      "repository": "https://github.com/Cosmian/kms",
      "path": ".github/instructions/lockfile-hashes.instructions.md",
      "ref": "6b3a44767d40c9826639aabacef0b4233ce2d62e",
      "url": "https://github.com/Cosmian/kms/blob/6b3a44767d40c9826639aabacef0b4233ce2d62e/.github/instructions/lockfile-hashes.instructions.md",
      "key": "Cosmian/kms/.github/instructions/lockfile-hashes.instructions.md"
    },
    "applies_to": "Cargo.lock, ui/pnpm-lock.yaml"
  },
  "instructions": "# Lockfile → Nix vendor hash sync\n\nWhen a lock file changes, the Nix vendor hashes must be updated to match.\n\n## Checklist\n\n- [ ] Update `nix/expected-hashes/` files with the correct `sha256-...` hash from CI output\n- Hash files: `server.vendor.{static,dynamic}.sha256`, `cli.vendor.{static,dynamic}.{darwin,linux}.sha256`, `ui.vendor.{fips,non-fips}.sha256`, `ui.pnpm.{darwin,linux}.sha256`\n\nWhen CI reports a hash mismatch, first verify the lock file changed **intentionally** in this PR;\nif not, revert it.\n\n> Rule 4.11 of `/kms-sync-rules`. For the full Nix workflow, see `nix.instructions.md`.",
  "cost": {
    "context_tokens": 149
  }
}

Fetch it by URL: GET /api/v1/registry/cosmian-kms-lockfile-hashes-instructions/manifest?version=1.0.0

About

Lockfile → Nix vendor hash sync

Checklist

Use it

Manifest

Reviews