Repository navigation
chore(release): prepare same-base 0.9.3 release candidate #163
Description
Parent: https://github.com/MachineWisdomAI/WisdomHelm/issues/93
Merge when clean: yes
Prepare FAVA0.9.3's ecosystem-correct immutable RC source/artifact path from fixed Mondaycutoff tested merged ed59cd4. Actual stable0.9.2; product source0.9.3 already bumped in ORIGINAL156, exact postmerge Tests41843534872SUCCESS and independent source review/package/MCP proofs retained. Do NOT repeat the semantic base bump, substitute movingmain or publish stable as an RC. Existing release.yml requires tag=sourcepackageversion and current-main for first publication, so v0.9.3rc1 cannot be falsely tagged on source0.9.3.
Read AGENTS/current version/release-channel policy, local updater and tests. First inspect supported exact-source RC preparation mechanism. Implement the smallest reviewed metadata-only candidate preparation retaining base0.9.3 and product bytes from ed59cd4; prepare synchronized PEP4400.9.3rc1 mirrors through supported local tooling. If current Version policy has no supported same-base RC metadata path, diagnose exact conflict and implement only a narrowly tested release-metadata case through normal source review, preserving product-bump semantics, current-main freshness, no product changes/version skips. Do not independently increment to0.9.4, set a distant expiry, alter promotion authority or weaken checks. Include release-channel/version-policy tests that reject product changes in metadata-only preparation, exact non-version-product-byte comparison vsed59cd47, candidate wheel/sdist package identity and smoke/MCP proof. Separate source preparation from publication; return exact PR/head/base/tests/rollback artifacts and gaps, no worker tag/release/PyPI/install/model/provider/data/config activation. FirstOfficer independently reviews/merges then publishes/installs only qualified exact artifacts under existing authority.
Nov9 duplicate/currentcapacity checks: no matching open FAVA source candidate task, zero active builders. Keep ongoing localLaya/feature work separate. Max2maintenanceworkers, existing6daywindow/24h2000turnattempt/10repairs/unattendedmode; onepass/currentdailyWedheartbeat continuation, no watcher/queue/schedulerchange. Current exact deadline from installedHelmet status governs. No major release or runtime restart.
Activity
timeleft-- commentedon Nov 11, 2026
Candidate preparation delivered through PR #164. First Officer independently reviewed exact a5e0556 (formal approval 5856211201), verified current checks/rules/threads/freshness, and used the repository's normal guarded merge: 520daec at 2026-11-11T08:58:45Z. Exact postmerge Tests 42991308332 and tag-push Tests 42991388082 succeeded.
The narrow same-base RC metadata path preserves version-normalized package bytes from ed59cd4. Independent frozen installation, 110 release/MCP tests and wheel/sdist identity checks passed. No repeated semantic base bump.
Subsequent release run 42991666643 succeeded using the supported protected-main dispatch with immutable tag input v0.9.3rc1. GitHub prerelease published 2026-11-11T09:05:49Z; the downloaded wheel and sdist match PyPI and candidate-SHA256SUMS:
The mapped host uv tool now runs 0.9.3rc1: all 66 package files match, all dependency pins remain unchanged, and isolated actual MCP initialize/17 tools/guide/save-recall/governed-draft checks passed. Prior 0.9.2 wheel, constraints and restore command are preserved. No application data, model/provider configuration, remote service or Docker runtime changed. Stable/latest remains 0.9.2; this is late candidate delivery, not stable promotion or a multi-day soak claim.
The initial dispatch from the tag was rejected by the existing protected-branch environment rule before any steps. It caused no publication; the supported main dispatch succeeded with the configured environment approval and unchanged protections. No further source work remains for this preparation issue.