Add release tooling: release-crispritz skill, RELEASING guide, CHANGELOG, prepare_release.py

[lucapinello]

What this adds

Release tooling for CRISPRitz that mirrors what CRISPRme already has, so a maintainer can cut a CRISPRitz release to Bioconda and then repin CRISPRme to it.

• .claude/skills/release-crispritz/SKILL.md — end-to-end release skill: (a) version-consistency pre-flight across crispritz.py / conda/meta.yaml / Dockerfile / git tag; (b) update CHANGELOG.md; (c) create the GitHub release/tag vX.Y.Z; (d) update the Bioconda crispritz recipe (version + sha256 + build.number: 0) — CRISPRitz is compiled, so autobump opens the PR but the build CI must pass on linux-64 + linux-aarch64 and a Bioconda maintainer merges; (e) the cross-repo repin: bump crispritz_version in CRISPRme's Dockerfile AND the crispritz X.Y.Z pin in CRISPRme's Bioconda recipe, then cut a CRISPRme release; (f) verify install on both arches.
• docs/RELEASING.md — human-readable guide with a crispritz → Bioconda → CRISPRme-repin diagram and the compiled-package caveat (arm64 must build).
• CHANGELOG.md — Keep a Changelog, seeded [2.7.0] + prior tags, plus an [Unreleased] entry for the pending #105 fix + CI + the stale-.pyc cleanup.
• scripts/prepare_release.py — idempotent version bump across the version-pinned files (crispritz.py, conda/meta.yaml; Dockerfile skipped when it holds no pin), computes the sha256 of the GitHub release tarball, and prints the meta.yaml diff + changelog scaffold + cross-repo reminder. Mirrors CRISPRme's scripts/prepare_release.py.

The chain this documents

git tag vX.Y.Z → GitHub release tarball → Bioconda recipes/crispritz/meta.yaml
   (sha256 of tarball; COMPILED → build CI must pass on linux-64 + linux-aarch64)
        → crispritz X.Y.Z live on Bioconda
        → CRISPRme repin (Dockerfile ARG crispritz_version + recipe `- crispritz X.Y.Z`)
        → CRISPRme release

sha256 test result (proves the flow)

Downloaded the live v2.7.0 tarball (https://github.com/pinellolab/CRISPRitz/archive/v2.7.0.tar.gz — the exact URL form the Bioconda recipe uses), computed its sha256 via prepare_release.py, and compared it to the live crispritz Bioconda recipe:

• computed: 89edad0570e3766c41184139197320aae1263f8d91fbc8c30f12105329d67377
• bioconda: 89edad0570e3766c41184139197320aae1263f8d91fbc8c30f12105329d67377
• MATCH ✅ (67,990,972 bytes)

Also verified prepare_release.py for a fake next version edits only the intended version files and is idempotent on re-run, then reverted.

Notes

• CRISPRitz version currently lives in crispritz.py (VERSION = "...") and the in-repo conda/meta.yaml stub. The authoritative recipe is on bioconda/bioconda-recipes (recipes/crispritz/meta.yaml); the in-repo conda/meta.yaml has drifted (stale version + old InfOmics URL) and is treated as advisory. The pre-flight step exists to catch exactly this drift.
• This PR is tooling/docs only — no version bump and no release are performed here.

cc @ManuelTgn

🤖 Generated with Claude Code