Skip to content

release: prepare RoleWeave 0.5.0 for local Windows upgrade #592

Closed

Description

@PeterGuy326

R1 / DEC: prepare a local Windows x64 upgrade from 0.4.0 to 0.5.0, consolidating the recent agent work requested by the owner. The new local client integration is an additive capability, so the candidate uses the next MINOR version under the repository SemVer convention.

Baseline: main 4cf36db (UI consolidation PR #591). The preparation PR adds the local Agent preflight and Qwen Office connection, resolves their overlap with compact employee settings, synchronizes package versions and frozen notes, and records validation.

Channel Scope
Local Windows installer Required: roleweave-0.5.0-x64.exe, metadata checksum verification, installed version and startup smoke.
npm N/A: the root and desktop packages are private; this request does not publish npm packages.
GitHub Release N/A for this local candidate: the owner requested a local package and upgrade. Public tag creation and updater-feed publication are outside this request. The existing public distribution channel remains available at v0.4.0.
GHCR N/A: this desktop candidate does not declare a container image.

Validation gates: protected preparation PR with all required CI checks; build from its exact merged main commit; Windows installer/metadata integrity; installed app reports 0.5.0 and starts successfully. Close old installed/development instances and remove obsolete local package outputs and merged temporary branches after verification.

Risk: native client integration adds local IPC and WSL lifecycle behavior. Qwen Office owns its tools, approvals, model and usage; RoleWeave must display those limits accurately. Preserve workspace and user-data directories during installation and cleanup.

Rollback: reinstall the immutable published 0.4.0 installer from GitHub if startup or workspace compatibility fails. Do not move existing tags or replace published assets. Append the final PR, main commit, installer SHA-256, installation and cleanup receipts here.

Completion receipt — 2026-10-12 (Asia/Shanghai):

  • UI consolidation: PR feat(desktop): refine employee settings and rich conversation replies #591. Final upgrade consolidation: feat(agents): consolidate local client connections and prepare 0.5.0 #593, merged as 9b80e94.
  • Duplicate source PR feat(agents): connect Qwen Office desktop and validate local Codex CLI #594 was closed after all changes through 2e49a7f were collected into feat(agents): consolidate local client connections and prepare 0.5.0 #593.
  • All PR CI checks passed on final head f70cf12: https://github.com/bytefolk/roleweave/actions/runs/38158040778. Linux/macOS full checks, security checks, native staging, installers and layout parity succeeded.
  • Windows installer rebuilt from the exact merged main commit. roleweave-0.5.0-x64.exe is 114493043 bytes; SHA-256 e5e219b8e14586f976a2ac7f52e62cf021840d80d9852d0cf66455e1bdde924c. The installer verifier confirmed latest.yml version, size and SHA-512 integrity.
  • Per-user installation reports 0.5.0; the main application window was created and remained running. User-data files were retained; configuration, service-connection and WSL-setting hashes were unchanged across startup.
  • Both old 0.4.0 development staging directories were removed. The installed old application was replaced, the updater cache now contains 0.5.0, and only the current distribution build remains in the inspected checkout release directories. Temporary consolidation branches and the old session build overlay were removed. Primary Windows and WSL main checkouts were synchronized.
  • A separate clean-copy smoke run left an input-method helper holding its temporary directory. Automatic approval rejected terminating that helper and cleaning the directory (blocked by policy; no detailed reason). The residual test directory was left intact. Native GitHub startup smoke passed, and the actual installed application startup and resource hashes were checked separately.
  • No public tag, GitHub Release or updater-feed publication was performed for this local candidate.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions