fleet-reordering-release-bump

To move a git release bump commit to the tip, you reorder the commit history so the bump becomes the latest commit. The skill validates tree identity, creates a timestamped backup branch, and uses a safe lease-based push to ensure repository contents remain unchanged.

The safest way to retag a vX.Y.Z release after reordering commits is using git update-ref. This approach moves the tag to the relocated bump commit while preserving identical tree content and creating a timestamped backup branch before making changes.

Yes, you can relocate a release bump when later commits have landed on top of it. The relocation process moves the bump commit to the tip, retags the version, and validates that only package.json and CHANGELOG entries are affected.

To ensure git tree contents stay identical when reordering a release bump, the process checks tree identity before and after the relocation. It enforces that only package.json and CHANGELOG entries are moved and performs a safe lease-based push.

When relocating a release bump commit, the process enforces that only package.json and CHANGELOG entries are moved. This validation ensures no other repository content is altered during the commit reordering and retagging operation.