Repository navigation
chore(release): prepare RoleWeave 0.6.0 (#623) - #624
Merged
Merged
Conversation
Refs #623. Consumed revision: R1 (DEC-ROLEWEAVE-623-001). Synchronize release versions, downloads and frozen notes for the six main commits after v0.5.0. Correct the preflight ledger placement and remove a stale changelog conflict marker.
Refs #623. Consumed revision: R1 (DEC-ROLEWEAVE-623-001). Wait for the loaded material control before checking criterion text so the assertion cannot retain a node removed by the initial loading render. Preserve the metadata-only resolver and no-body-read/no-goal-write checks.
8 of 12 tasks
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.
Tracking record
Refs #623. Consumed revision: R1 (
DEC-ROLEWEAVE-623-001). Keep the release record open until publication and independent channel verification finish.Summary
Prepare RoleWeave 0.6.0 from main
b69b9d8a2a0271b0084e38670e1add22b1454640, covering all eight commits after v0.5.0. Synchronize the five root/desktop package and lockfile version fields, versioned downloads, the changelog and frozen release notes. Document versioned task briefings, explicit task collaborators/dependencies, relay handoff snapshots, task execution progress, delivery preflight, optional approval aging advice and Codex model/prompt fixes, including the local record downgrade limitation.Stabilize the existing delivery-preflight panel test: await the loaded material checkbox before asserting criterion text. The initial loading render can remove a criterion node between an async query and its assertion. Keep all metadata-only/no-body-read/no-goal-write checks. No application behavior, dependency version or publishing workflow changes.
Move the preflight entry incorrectly appended to the 0.5.0 ledger into 0.6.0 and remove the stray changelog conflict marker. Preserve the frozen v0.5.0 release notes.
Acceptance criteria
Validation ledger
Tests and coverage
npm run checkgate passed on the final head. Server tests use an unprivileged user and isolated network namespace because this host offers only 301 ephemeral ports and root invalidates permission fixtures. Only namespace-local network settings changed. Two server/renderer workers bound resource contention; an earlier probe timing failure and all original evidence remain in release: publish RoleWeave 0.6.0 desktop clients #623.Change classification
Risk and rollback
Publication advances both updater feeds. Stage counts describe execution phases; completion does not replace delivery acceptance. Delivery preflight and Laya advice retain their existing opt-in boundaries and cannot make acceptance/approval decisions.
Back up the workspace before upgrading. Stop on a failed release gate. Before publication, revert preparation through a reviewed change if needed. After publication, keep the 0.6.0 workspace intact; if reverting the app, use immutable v0.5.0 with a copy of a pre-upgrade backup or a separate workspace. Correct defects in a new patch version. Never replace released bytes or move/reuse a tag.
Breaking or security notes
Pre-1.0 preview. Relay and project collaboration add optional
GroupMessage.relaySteps,TurnRecord.relayHandoff,TurnRecord.taskBriefing, andGoalWorkItem.participants/dependsOnfields. New readers accept old records, but older strict readers can reject new records. Do not strip stored handoff evidence to simulate downgrade compatibility.Installers retain the existing OS-unsigned channel and separately signed macOS update metadata. Model discovery does not establish inference entitlement or change account/billing mode.
Author checklist
Reviewer notes
The owner explicitly directs merge, tagging and publication after being informed independent approval was missing. This release records that owner-directed exception to the normal release process, without fabricating a reviewer approval. Current-head checks must remain green and server-side settings must be preserved. There are no unresolved review threads. Protected main requires one independent approval and five required checks; no repository CODEOWNERS file is present.
Active immutable-release-tags ruleset 22240705 forbids update/deletion of refs/tags/v* with no bypass actors. Active release-tag-creation ruleset 22240738 restricts creation to its designated RepositoryRole 5 actor. The current Bindy-lbb identity may create tags and cannot bypass immutable update/deletion. Keep these controls intact.
After protected merge, record the exact squash SHA and successful checks for that commit, recheck version absence, main ancestry and protections, then create one annotated v0.6.0 tag. Existing release.yml builds both native distributions, signs macOS update metadata, verifies the draft inventory and publishes last. Independently verify the published assets and append the receipt to #623 before closing it.