Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Recovering from a failed release

If a release fails midway through (e.g., cargo publish fails due to registry validation), you can cleanly revert the entire pipeline using Jujutsu’s operation log:

  1. Find the operation right before you ran jj-release (look for the Release: please commit):
jj op log
  1. Restore the repo to that operation:
jj op restore <operation_hash>
  1. Discard the mutated files (like Cargo.toml bumps) from your working copy:
jj restore

Note

jj-release runs cargo publish --dry-run as a pre-flight check, but this only validates local compilation. Server-side registry rejections (like invalid URLs or missing permissions) will still cause the pipeline to fail during the final push.


Fixing commit messages after a release (Immutable Commits)

If you need to fix a typo in a commit message after a release is finalized (which marks the commit as immutable), rewriting the message will detach the Git tag. Because changelog generators rely on Git tags to group history, you must re-anchor the tag to the new timeline before regenerating the changelog.

  1. Rewrite the commit message:
jj --ignore-immutable desc -r <commit_rev> -m 'fix: your new message'

(Note: use single quotes ' if your message contains backticks so your shell doesn’t execute them). 2. Find the new release commit hash: Because history is rewritten, the release commit generated a new hash. Find it using jj log. 3. Re-anchor the release tag (i.e. The commit chore: release vX.Y.Z):

jj tag set vX.Y.Z -r <NEW_RELEASE_HASH> --allow-move

(Note: the further back in history you go, the more tags you’ll have to re-anchor) 4. Regenerate your changelog. The generator will now traverse the corrected timeline and parse the updated messages.

rm CHANGELOG.md
jj-release changelog --full -o CHANGELOG.md
  1. Push/Force-push the corrected history. Since you altered public history, force- push the updated branch and tag back to your remote.
# Push the corrected bookmark (no force need if jj handles the move)
jj git push

# Force-push each re-anchored tag via git directly
# (jj git push doesn't support --force)
git push origin vX.Y.Z --force

Or if you have multiple tags to re-anchor, push them all:

jj git push # pushes the bookmark
# then for each re-anchored tag:
git push origin v0.1.0 --force
git push origin v0.2.0 --force
# etc.

Force-pushing is generally considered bad practice in collaborative projects since others may have fetched the old tags. For a solo project it’s fine, just keep this in mind..