Repository navigation
Record v0.2.0's release run in its In flight entry - #303
Merged
Merged
Conversation
Val decided on #290. The signed v0.2.0 tag passed release run 39100984341 on 2026-10-18. It covered signing, notarization and stapling, the packaged E2E suite, all three signed native updater scenarios and the Windows and Linux installers. The entry still listed the packaged E2E and the updater scenarios as remaining. It now records the run and the draft's assets. What is left: the download checks, publication, the banner upgrade on the release Mac and the Companion build 7 upload. The entry also said the release ships everything under "On main, unreleased". That stopped being true when the conversation-fidelity slices from #282 landed after the tag. It now says the tag is on 01b1b8a (#272) and that those slices are not in it. Every item it lists is in the tag. Coven-Harness: Claude Code / claude-opus-5-5
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This was referenced Oct 18, 2026
BunsDev
added a commit
that referenced
this pull request
Oct 18, 2026
Coven-Harness: Claude Code / claude-opus-5-5
BunsDev
added a commit
that referenced
this pull request
Oct 18, 2026
Coven-Harness: Claude Code / claude-opus-5-5
BunsDev
added a commit
that referenced
this pull request
Oct 18, 2026
Coven-Harness: Claude Code / claude-opus-5-5
BunsDev
added a commit
that referenced
this pull request
Oct 18, 2026
Coven-Harness: Claude Code / claude-opus-5-5
9 of 15 tasks
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Docs and plans steward (#290), following Val's decision there. Docs only, one In flight entry.
v0.2.0tag passed release run 39100984341 on 2026-10-18. Every job passed: signing, notarization and stapling; E2E against the packaged app; all three signed native updater scenarios; the Windows and Linux installers; and attaching the artifacts.01b1b8a(Prepare desktop 0.2.0 and Companion 0.2.0 (7) #272), so the conversation-fidelity slices from Carry native message identity, phases and outcomes from the CLIs into the transcript (CF-1) #282 onward aren't in it. The entry now says so. Every item it lists is in the tag: Run read-only routines on a timer #267, Ask Jev through one decision service #257, Notes: defects deferred from the stack's pre-merge review #241, Give every inline error Copy details and, where it helps, Retry #269, Make Analytics look like the rest of Modex and fit the window #248 and Keep Images refreshing a job that reaches approval before the submit reply #266, each checked withgit merge-base --is-ancestor.The "[Candidate review]" line that #286 anchors on is unchanged.
Verification
pnpm build && pnpm testpassed locally with no failures. Root suites: 109 and 16. Desktop: 1,524 passed and 16 skipped of 1,540, then 21. The remaining workspace suites: 10 and 16.