Repository navigation
Release proposal: v2.1.0 #499
Description
Automated release proposal from the reusable Release Prepare workflow.
- Proposed tag:
v2.1.0 - Previous tag:
v2.0.1 - Diff: v2.0.1...56715fd
- Proposed from:
56715fd3c2affbc2794c4259794d52a55316ba13
Draft changelog
Features
- feat(annex): add @zi-unregister-annex (feat(annex): add @zi-unregister-annex #503) (45c096f)
Fixes
- fix(unload): reach the Plugin Standard unload function (fix(unload): reach the Plugin Standard unload function #502) (5bf7cf1)
- fix(load): report the actual object-load status (fix(load): report the actual object-load status #500) (e18ad73)
- fix(release): install Zsh before verifying the release tag (fix(release): install Zsh before verifying the release tag #497) (8104e93)
Other
- test(unload): pin the ownership contracts that already hold (test(unload): pin the ownership contracts that already hold #504) (a3f2e76)
- refactor(core): remove the duplicate helper and correct drifted headers (refactor(core): remove the duplicate helper and correct drifted headers #501) (3a0d632)
To publish
Per ADR 0007 the signed annotated tag is the publication boundary. Review and adjust the version if needed, then:
git switch main && git pull --ff-only
# bump any in-repo version metadata first, if this repository has it
git tag -s v2.1.0 -m v2.1.0
git push origin v2.1.0Updated automatically on every push to the default branch; closing this issue without tagging skips the release.
Activity
[-]Release proposal: v2.0.2[/-][+]Release proposal: v2.1.0[/+]ss-o commentedon Sep 3, 2026
Published as v2.1.0: https://github.com/z-shell/zi/releases/tag/v2.1.0
The proposed version is taken as computed.
feat(annex): add @zi-unregister-annex(#503) is a new public API, so a minor bump is the accurate description, unlike v2.0.1 where the onlyfeatcommits werefeat(ci)andfeat(release)and the consumed surface carried fixes only.The tag is signed and verified, targets
56715fd3c2affbc2794c4259794d52a55316ba13, and the four workflows the verifier requires were green at that commit before it was pushed.Worth recording: the
Releaseworkflow completed on its own this time. Its previous run, onv2.0.1, was its first ever execution and failed because the publish job ran the verifier under Zsh without installing it. That fix (#497) reachedmainwith the #498 promotion, and this release is the first to exercise it successfully end to end.