aboutsummaryrefslogtreecommitdiff
path: root/.pi
diff options
context:
space:
mode:
authorOgulcan Celik <ogulcancelik@gmail.com>2026-05-29 21:50:53 +0300
committerOgulcan Celik <ogulcancelik@gmail.com>2026-05-29 21:50:53 +0300
commit4219aec638cdd81efae6460c6fba28418925c37c (patch)
tree7a0323281cf343d6a5bd567d6bc5fa69e201a666 /.pi
parent20e26271c92be01aa726bc6827d93ad8512483c9 (diff)
fix: update nix release hash
Diffstat (limited to '.pi')
-rw-r--r--.pi/prompts/pre-release-audit.md4
1 files changed, 4 insertions, 0 deletions
diff --git a/.pi/prompts/pre-release-audit.md b/.pi/prompts/pre-release-audit.md
index 4858f598..3e851d54 100644
--- a/.pi/prompts/pre-release-audit.md
+++ b/.pi/prompts/pre-release-audit.md
@@ -70,6 +70,7 @@ Process:
8. Verify finalization state.
- Before `just release`, approved `docs/next/README.md` must be copied to root `README.md`, approved staged website docs must be copied from `docs/next/website/src/content/docs/` to `website/src/content/docs/`, and the deleted root doc files must stay deleted.
+ - If the release will change `Cargo.lock` or the package version, check `nix/package.nix` after the release version bump and refresh `cargoHash` before tagging. A stale hash fails both the `Nix` workflow and the release workflow's `flake-check` job with a fixed-output derivation mismatch. Use the `got:` hash printed by `nix flake check --print-build-logs` or CI, then rerun the Nix check when available.
- Run or recommend:
```bash
just release-docs-check
@@ -112,6 +113,9 @@ Accepted/no action:
Root docs finalized: YES | NO
<result of just release-docs-check or why it was not run>
+Nix cargoHash: OK | NEEDS UPDATE | NOT CHECKED
+<result of nix flake check or the hash-refresh status>
+
Required before release:
1. <short action>
```