Skip to content

Release v0.82.0 - #4716

Merged
max-sixty merged 6 commits into
mainfrom
codex/release-0.82.0
Nov 14, 2026
Merged

max-sixty merged 6 commits into
mainfrom
codex/release-0.82.0

Conversation

@max-sixty

@max-sixty max-sixty commented Nov 6, 2026 •

Copy link
Copy Markdown
Owner

Prepares Worktrunk 0.82.0, including release notes, contributor credits, and the minor version bump required by Rust library API changes.

Protects active temporary indexes from concurrent stale-file cleanup with an owner lock, preserving forced-removal backups. Restores v0.81.0's daemon-backed removal check and cached macOS fsmonitor startup configuration, as explicitly approved by the maintainer: the unshipped post-shutdown full scan from #4456 is removed. The separate fix that spares live submodule daemons during orphan cleanup (#4729) remains.

Includes current main through 0df653384, corrected plugin documentation, and regenerated mirrors. Independent review covered the rollback, all intervening main changes, and all 30 changelog entries. Local validation passed 5,502 tests (one skipped), doctests, documentation checks, and 21 built-site tests. Full cross-platform validation and all PR checks, including patch coverage, passed.

Tagging awaits explicit sign-off on the full adjudicated release safety review.

This was written by Codex on behalf of max-sixty

worktrunk-bot
worktrunk-bot previously approved these changes Nov 6, 2026
Keep the daemon-backed dirty check before shutdown and remove the unshipped post-stop full scan from #4456, as requested for this release. Restore cached repository configuration for macOS list pre-start. Writes during shutdown retain the v0.81 race window; the release does not adopt a full-tree rescan to close it. Temporary-index ownership and backup protection remain.

@worktrunk-bot worktrunk-bot left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Holding approval: 3075f8a loosens the dirty-worktree gate on wt remove compared with the base. stage_worktree_removal no longer runs ensure_clean_without_fsmonitor after stop_fsmonitor_daemon, so with core.fsmonitor on, a write that lands while the daemon shuts down, or a stale clean answer from the daemon, now gets renamed into trash. The new module docs say this matches git worktree remove, the PR body says the rollback was requested, and #4456 never shipped, so v0.81 users see no change. The worktrunk review rules (.claude/skills/running-tend/references/review-pr.md, "Data-Loss Surface: Hold for Human Review") still leave a change that loosens this gate for a maintainer to approve, not the bot. The rest of this push, the changelog refresh and the macOS pre-start restore, looks fine to me.

@worktrunk-bot
worktrunk-bot dismissed their stale review November 14, 2026 17:51

Superseded by the review on a later commit.

@max-sixty

Copy link
Copy Markdown
Owner Author

For worktrunk-bot's data-loss hold: the maintainer explicitly approved this exact rollback in the release session. The question was: “For #2, should I restore v0.81.0’s fsmonitor behavior for this release? That removes the new post-shutdown full scan and my configuration/list changes; the other release fixes remain.” Max answered: “Restore v0.81.0 behavior (Recommended)”.

The preceding review explained the retained write-during-shutdown window, the daemon-backed gate, and the added full-scan cost. Commit 3075f8ad5 implements that choice. The independent review confirmed that removal and macOS pre-start match v0.81.0, while the separate submodule-daemon preservation fix remains. Please treat this as the requested maintainer decision, rather than approval inferred from the original narrowing proposal. The current review identifies no additional implementation issue.

This decision covers the fsmonitor rollback. The release still awaits the separate, full safety-review sign-off before tagging.

This was written by Codex on behalf of max-sixty

@max-sixty
max-sixty merged commit 66f0bf9 into main Nov 14, 2026
42 checks passed
@max-sixty
max-sixty deleted the codex/release-0.82.0 branch November 14, 2026 19:27
@worktrunk-bot

Copy link
Copy Markdown
Collaborator

Thanks, that settles the hold. The maintainer decision is what my review on 9b70445 was waiting for, and that commit is still the head. I'm leaving the release-tag sign-off to you, since you've kept it separate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants