Release

Derive the version, promote develop to main, and verify every channel and every file a release publishes. Run automatically, this prompt is a drill: it verifies that each step below still holds and changes nothing.

Rendered from the repository at vibey-engine 4.4.0; regenerated by scripts/continuation_prompts.py, do not edit inside these markers.

  • Mode when GitHub runs it weekly: drill — verifies and reports; changes nothing.
  • What it is for: Derive the version, promote develop to main, and verify every channel and every asset.
  • Decision records: 88, the newest 0088 — TypeScript, never JavaScript: the only authored form is typed, and the JavaScript that must exist is generated.
  • Lanes it keeps usable: Promote, Release, krypton-app, GitHub Release, Release binaries, Release surfaces, Open VSX.
  • Agent skills it relies on: .claude/skills/vibey-releasing/SKILL.md.

The prompt

You are preparing or verifying a release of vibey (https://github.com/the-vibey-project/vibey).
Your working directory is a clone of it. Assume you remember nothing. Read
.claude/skills/vibey-releasing/SKILL.md in full before anything else: it is the procedure.

The version is derived, never chosen.
1. `git fetch origin` and derive at the real tip, never a stale local checkout:
   `git switch --detach origin/develop` then `uv run vibey-gh version --since origin/main --explain`.
   A change under [version] content_paths in .vibey-gh.toml is a minor release; code_paths a
   patch; a breaking marker anywhere in the range makes it major.
2. Check develop is releasable: the latest CI run on its tip is green, no workflow is red
   (docs/continuation/keep-green.md), and no commit between main and develop carries a
   skip-ci marker (`git log origin/main..origin/develop --format=%B`).
3. Promotion is a person's decision. If you are running unattended, STOP here and report
   the derived version and the readiness evidence. With a person's go-ahead:
   `gh workflow run promote-to-main.yml --ref develop -f dry_run=false` opens the
   `chore(release): X` pull request into main; a person merges it (rebase only).
4. After the merge, verify everything, by evidence:
   - PyPI: `pip install vibey-engine==X` in a fresh venv; `vibey --version` prints X, and every
     console script in pyproject.toml [project.scripts] is on PATH. Same for krypton-app.
   - The GitHub Release vibey-vX: every declared file is attached (docs/guides/downloads.md),
     every file matches SHA256SUMS (`shasum -a 256 -c SHA256SUMS`), and every file verifies
     with `gh attestation verify <file> --repo the-vibey-project/vibey`.
   - Open VSX lists the-vibey-project.krypton at the extension's version.
   - The site, paper and book answer 200 under https://the-vibey-project.github.io/vibey/main/.
5. Report each check with its result. A check you could not run is "not verified", never
   "passed". Never publish, tag, yank or delete anything by hand.