Repository navigation
Description
Decision and scope
The owner explicitly approved creation and linkage of this public governing record for the one-off formal v0.2.0 release prepared in #442. The requested release is stable, not a draft or prerelease; highlights compare against v0.1.1. The assistant is preparing the release under hsliuustc0106. This record does not substitute for independent PR approvals or bypass branch protection.
Acceptance
- Merge the reviewed preparation PR only after required CI and two independent eligible write-account approvals; retain unresolved review concerns until reviewers clear them.
- Keep scheduled/default preview policy and pyproject settings unchanged. After v0.2.0, ordinary changed-source planning naturally chooses v0.2.1 preview.
- Use the manual-only exact v0.2.0 path on reviewed main, first with dry_run=true. Hongsheng Liu (hsliuustc0106) is the release decision owner for the subsequent dry_run=false publication; the assistant must not infer that this issue or a reviewer comment independently authorizes dispatch.
- Bind tag and all packages to the planned source commit. Deliver wheel, sdist, Codex plugin ZIP, WorkSwarm plugin ZIP and SHA256SUMS.
- Require source/ancestry and reservation checks, CPU tests/lint, build/twine/sdist validation, clean installed-wheel/version parity, both extracted plugin validations and downloaded checksum verification. Recheck current release state immediately before publication; no overwrite of reserved tags, releases or assets.
- Use reviewed highlights since v0.1.1 with actual packaged tasks and README examples; retain FAIL/INCONCLUSIVE qualifications. Software checks are not GPU/NPU model-quality or performance validation.
- Verify published release is draft=false, prerelease=false, points to the intended tag/commit, and has all five artifact classes.
Current status
PR #442 head 19b38de. Focused tests: 210 passed; lint and diff checks passed. Initial exact-head CI matrix passed. Fresh Ready run is still in progress: https://github.com/InferMatrixLab/InferRSI/actions/runs/43599786640 . No release dispatch, merge, tag creation or publication has occurred for v0.2.0.
Boundaries and cleanup
The one-off path intentionally remains fail-closed after v0.2.0 is reserved/published. Cleanup can be proposed and reviewed separately after release, not silently folded into this release decision. No permission expansion, paid model calls or hardware campaigns are authorized by this record.
Activity
amy-why-3459 commentedon Nov 14, 2026
Thanks for recording this. It covers what I asked for on #442:
dry_run=falsepublication, after adry_run=truepass on reviewed main.I've approved #442 at
19b38de8fa13a3a0d6e7375306cf396cd511f7eb. That approval covers the preparation code only, not dispatch.One suggestion for the follow-up cleanup: once v0.2.0 is published, remove the
release_v020input, the planner flag and the fourRELEASE_TAG == v0.2.0checks inrelease.yml, or keep them with a note that they are intentionally fail-closed. A cross-link from here would make that easy to track.Dong1017 commentedon Nov 17, 2026
Posted by an agent on behalf of @Dong1017 (incremental only; points already raised by others or decided by the owner are not repeated).
Incremental note: v0.2.0 is published and its assets check out, but the
dry_run=truepass ran on a different commit from the one that was published. The "Current status" section still says nothing has been published.draft=falseandprerelease=false, and the tag points at223ee523115d8d59eebf4568fd6ac34f4708b1d4. All five artifact classes are attached (wheel, sdist, Codex ZIP, WorkSwarm ZIP,SHA256SUMS). I downloaded them, andsha256sum -c SHA256SUMSpassed for all four packages. The wheel METADATA saysVersion: 0.2.0.86435c12(the release: prepare one-off formal v0.2.0 with reviewed highlights #442 merge), and itspublishjob was skipped. The publishing run 43602273847 ran on223ee523, which is one commit later: Compose standalone knowledge reads in Apps #436 "Compose standalone knowledge reads in Apps" was merged at 13:53 UTC, between the two dispatches. The publishing run did run its own build, CPU checks, clean-install and plugin validation on223ee523. Whether that satisfies "first with dry_run=true" on the published source is a call for the release decision owner (@hsliuustc0106), and the issue should record that call..github/workflows/release.ymlon main1acfacf8still has therelease_v020input (L9) and theRELEASE_TAG == v0.2.0branches (L167, L255, L267, L277), and no cleanup issue is linked here.Scope: GitHub release API and assets, the two
release.ymlrun job and step lists, commit ancestry on main1acfacf8. Unverified: the workflow_dispatch inputs (not exposed by the runs API). I inferred that the first run was the dry run because itspublishjob was skipped.zengchuang-hw commentedon Nov 17, 2026
Independent release-boundary review (not a publication authorization)
Reviewed current main
1bbc3b0c8de14d6194d7ee7987607365b665fbfeagainst the one-off v0.2.0 scope and the release tag's source223ee523115d8d59eebf4568fd6ac34f4708b1d4. I did not use other reviewers' comments as evidence.The one-off publication is already observable: v0.2.0 was published on 2026-11-14 at 14:03:33 UTC with
draft=false,prerelease=false; its tag resolves directly to the source above. Its asset inventory contains the wheel, sdist, Codex ZIP, WorkSwarm ZIP and SHA256SUMS. Release run 43602273847 is successful at that SHA, including the build/package, isolated installed-wheel, plugin validation, checksum and publisher steps. These are observed GitHub status records, not a claim that I independently rebuilt those uploaded bytes.Source checks:
python -m pytest -o addopts='' -q -p no:cacheprovider tests/test_release.py tests/test_release_publisher.py: 70 passed. These exercise planner guards and the actual publisher shell against mocks, not live publication.Conclusion: no additional release-boundary implementation blocker found in this focused check. The published-state evidence supports recording the one-off outcome rather than issuing another publication decision.
Limits: I did not independently verify the preparatory PR's two eligible write-account approvals, the separate dry-run/authorization sequence, download and recompute the published asset hashes, rebuild all distributions, run the full test suite, or exercise native host UIs/GPU/NPU workloads. Those are not implied by this comment or by the successful workflow status. No tag, release, asset, dependency, repository setting or publication action was changed by this review.