Release v19.0.1 with safe retained-state migration guidance #831

Activity

1. flyingrobots

   added this to the v19.0.1 milestone on Jul 28, 2026
2. flyingrobots

   added

   type:releaseRelease operation or release gate work.Release operation or release gate work.

   priority:asapImmediate release pressure.Immediate release pressure.

   status:activeSomeone is actively working this issue.Someone is actively working this issue.

   area:releasePrimary work area: release.Primary work area: release.

   on Jul 28, 2026
3. coderabbitai commented on Jul 28, 2026

   

   coderabbitaibot

   on Jul 28, 2026 – with coderabbitai

   Last edited by coderabbitai

   More actions

   🔗 Related PRs

   #674 - Prepare v18.1.0 release [merged]
   #788 - Add one-shot v18-to-v19 retained-substrate migration [merged]
   #802 - Release v19.0.0 [merged]
   #829 - Make v19 generation and migration guidance executable [merged]
   #832 - Release v19.0.1 with safe migration guidance [open]

   ---

   📝 Issue Planner

   _{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

   • Create Plan

   ---

   🧪 Issue enrichment is currently in open beta.

   You can configure auto-planning by selecting labels in the issue_enrichment configuration.

   To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

   issue_enrichment:
     auto_enrich:
       enabled: false

   💬 Have feedback or questions? Drop into our discord!
4. coderabbitai

   added

   area:docsPrimary work area: docs.Primary work area: docs.

   area:storagePrimary work area: storage.Primary work area: storage.

   area:testingPrimary work area: testing.Primary work area: testing.

   on Jul 28, 2026
5. flyingrobots

   added

   priority:nextNext in line after active work.Next in line after active work.

   and removed

   priority:asapImmediate release pressure.Immediate release pressure.

   on Jul 28, 2026
6. flyingrobots commented on Jul 28, 2026

   

   flyingrobots

   on Jul 28, 2026

   MemberAuthor

   More actions

   v19.0.1 release evidence and retrospective

   Publication

   • PR Release v19.0.1 with safe migration guidance #832 merged with a merge commit after all required checks passed and CodeRabbit approved with zero review threads.
   • Reviewed/tagged commit: e35703deb3a76a1ab68548f588901f03a209a900.
   • Main-push tag gate: https://github.com/git-stunts/git-warp/actions/runs/30370896577
   • Release workflow: https://github.com/git-stunts/git-warp/actions/runs/30371699359
   • GitHub Release: https://github.com/git-stunts/git-warp/releases/tag/v19.0.1
   • npm and JSR both independently resolve 19.0.1 as latest. npm exposes a registry signature and SLSA v1 provenance.

   Public artifact smoke

   A clean temporary project installed exact @git-stunts/git-warp@19.0.1 with zero vulnerabilities. The root export was exactly Runtime; the README, architecture guide, v19 migration guide, operations guide, and API guide were present in the downloaded package; and git-warp-v18-to-v19 --help described the corrected one-pass default.

   The downloaded CLI then migrated the checked-in 2 MiB published-v18 fixture: two writers, 18 commits, retained checkpoint state, guarded scratch proof, atomic promotion, and complete recovery refs. The first run returned migrated with scratchVerified: true; the second returned already-current. ~/.think/codex was not touched.

   What went well

   Executable docs contracts caught stale version signposts, missing package docs, inaccurate source-mutation wording, and outdated settlement/API claims before publication. The branch, PR, main-push tag, and tag-level release gates each proved a distinct boundary. The bounded authentic v18 fixture gave a fast public-artifact proof without checking a huge repository into Git.

   What to improve

   npm pack and npm publish repeatedly invoke the full prepack test corpus, making release feedback slower than necessary; #826 owns that debt. JSR bootstrap repeatability remains tracked by #830. Think memory is still unreadable because of the mixed-format writer history, so the application/API port and authoritative repository rehearsal remain explicitly outside this package-release issue.

   No new BAD CODE™ or COOL IDEA™ fallout was discovered during publication; the relevant existing issues are #826, #830, and #828.
7. flyingrobots

   removed

   status:activeSomeone is actively working this issue.Someone is actively working this issue.

   on Jul 28, 2026
8. flyingrobots commented on Jul 28, 2026

   

   flyingrobots

   on Jul 28, 2026

   MemberAuthor

   More actions

   v19.0.1 is published and independently verified on npm, JSR, GitHub Releases, a clean consumer install, and a disposable retained-v18 migration fixture.
9. flyingrobots

   closed this as completedon Jul 28, 2026