Release operations: configure the PyPI Trusted Publisher for 0.2.0

[seonghobae]

External configuration blocker

ThreadWeave main is release-capable at commit 4030577a6018d5bef1ea6e9de201f32ac95a5bbc, and the threadweave project URL currently returns 404 on PyPI. Repository code cannot create or approve the PyPI account-side trust relationship.

The hourly NVIDIA NIM/OpenCode product-development workflow now stops fail-closed while this release-blocker issue remains open. PR review, repair, check revalidation, and merge continue normally, so release operations can proceed without unrelated product drift.

Before dispatching Release ThreadWeave with version 0.2.0, configure both sides of the identity boundary:

GitHub

• Create an environment named pypi.
• Limit deployment to the protected main branch.
• Add the independent approval policy required by the organization.
• Do not add a long-lived PyPI token.

PyPI pending Trusted Publisher

Configure these exact claims:

• Owner: ContextualWisdomLab
• Repository: ThreadWeave
• Workflow: release.yml
• Environment: pypi

Acceptance evidence

• The GitHub environment is visible and protected.
• The pending publisher exists under the account that will own threadweave.
• The workflow is dispatched from main with version=0.2.0.
• Build, SLSA provenance, SPDX SBOM attestation, annotated tag, immutable GitHub Release, and PyPI Trusted Publishing all succeed.
• https://pypi.org/project/threadweave/0.2.0/ exposes both wheel and sdist with PEP 740 provenance.
• A clean-environment install reproduces the documented THREAD and UID THREAD smoke example.

Do not manually upload distributions or add an API token to bypass a failed identity, digest, provenance, or environment check.

[seonghobae]

Automated release-readiness verification — 2026-08-04

• main is at 4030577a6018d5bef1ea6e9de201f32ac95a5bbc; its CI push run completed successfully.
• The open pull-request queue is empty.
• GitHub's repository-environments endpoint currently reports total_count: 0, so the required pypi environment is not yet configured.
• https://pypi.org/project/threadweave/ still returns 404, so no first release has established the project.
• The hourly NVIDIA NIM/OpenCode product loop is now frozen by this issue's release-blocker label; PR maintenance remains active.

The remaining work is account-side administration: create and protect the GitHub pypi environment, then create the exact PyPI Pending Trusted Publisher claims documented above. Do not close this issue until both are visible and the 0.2.0 release workflow succeeds end to end.

[seonghobae]

Autonomous loop checkpoint — 2026-08-05

• Open pull-request queue: 0.
• main remains at release-frozen commit 4030577a6018d5bef1ea6e9de201f32ac95a5bbc.
• PR release: prepare ThreadWeave 0.2.0 with trusted publishing #16 (0.2.0 trusted-release implementation) and PR ci: pause autonomous product work during release freezes #18 (release-freeze gate) are merged.
• The release-blocker label remains active, so the hourly NVIDIA NIM/OpenCode product loop correctly refuses unrelated source changes while PR maintenance remains available.
• This repository-scoped automation cannot create the PyPI account-side Pending Trusted Publisher or approve the GitHub environment protection policy. Issue ownership is now assigned explicitly to @seonghobae for those account-side steps.

After the exact GitHub pypi environment and PyPI publisher claims are visible, dispatch Release ThreadWeave from protected main with version=0.2.0. Do not remove the blocker, alter versioned source, manually upload artifacts, or use a long-lived PyPI token before the end-to-end workflow and clean-install smoke evidence succeed.

[seonghobae]

Release-readiness checkpoint — 2026-08-05

• main remains frozen at 4030577a6018d5bef1ea6e9de201f32ac95a5bbc for the 0.2.0 release.
• PR feat: add incremental mailbox threading with stable identity handoff #20 remains Draft and unmerged as required by this blocker.
• PR feat: add incremental mailbox threading with stable identity handoff #20 exact head 6cbfa46e12286d3c8a72ae7b6bce5586d17542cf now passes CI on Python 3.10–3.13, package/hash-install smoke, SAST Semgrep, and Security Scan; this does not alter the release ordering.
• The public PyPI threadweave project endpoint still returns 404, so there is no observable completed 0.2.0 publication.
• Repository-side automation still fails closed while this issue carries release-blocker.

The remaining acceptance path is unchanged: establish the exact PyPI Pending Trusted Publisher identity, satisfy the GitHub pypi environment policy, dispatch Release ThreadWeave from protected main with version=0.2.0, verify provenance/SBOM/tag/GitHub Release/PyPI artifacts and clean-install smoke, then close this issue. Do not use a long-lived PyPI token or manual upload as a bypass.

[seonghobae]

2026-08-05 release checkpoint

The post-release product branch has advanced to fb48d5e9b0de07b24e2dd70abf9f6d7a1d243cb2, but PR #20 remains draft and unmerged under this release freeze.

Code-side 0.2.0 release assets and the trusted-publishing workflow remain on frozen main. The account-side acceptance conditions in this issue are still authoritative: configure the PyPI Pending Trusted Publisher for ContextualWisdomLab/ThreadWeave, workflow release.yml, environment pypi; then dispatch the protected-main release and verify the published artifacts and attestations. No API-token or manual-upload bypass has been introduced.

While the account-side identity boundary remains open, PR maintenance continued. PR #20 now includes process-local concurrent-reader/writer serialization and fail-closed hostile snapshot handling. Its current exact-head CI and SAST gates are successful; Security Scan is still queued at this checkpoint. The release blocker remains open until the actual 0.2.0 publication evidence exists.

[seonghobae]

2026-08-05 release checkpoint

main remains frozen at the reviewed 0.2.0 release commit while PR #20 stays Draft. The current PR #20 exact head is fb48d5e9b0de07b24e2dd70abf9f6d7a1d243cb2 and has completed ci, SAST Semgrep, and the full Security Scan successfully. Python 3.10–3.13, package build/hash-install smoke, lock regeneration, OSV, Trivy, Scorecard, and dependency review are green; the exact-head Python 3.13 run reports 317 tests and 100% coverage over 1,988 statements and 720 branches.

This does not change the external release blocker. Before dispatching Release ThreadWeave for 0.2.0, the PyPI account that will own threadweave must contain the Pending Trusted Publisher with the exact claims already documented in this issue, and the GitHub pypi environment must satisfy the intended independent-approval policy. Do not dispatch without that identity boundary: the release workflow creates attestations, an annotated tag, and the GitHub Release before the final PyPI publication job.

After the verified 0.2.0 release succeeds, close this issue, update PR #20 to the released main, rerun every exact-head gate and the 100,000-message benchmark, obtain current-head independent review, and only then merge #20.

[seonghobae]

2026-08-05 final release-freeze checkpoint

PR #20 is now at exact head cf1cecbf1ca827eadd3fa4ff0b3dfb2a5cab71da. Exact-head ci, SAST Semgrep, and Security Scan all completed successfully across Python 3.10–3.13, package/hash-install smoke, and the trusted automation boundary. The latest product hardening rejects executable JSON container subclasses and cyclic built-in containers at snapshot restore without recursion or unbounded traversal; the full run reports 319 tests and 100% of 2,008 combined statements / 730 branches.

This does not change the release decision. PR #20 remains Draft and unmerged under this issue. The remaining gate is still the account-side PyPI Pending Trusted Publisher and the protected-main 0.2.0 release evidence specified above. No API token, manual upload, or release-order bypass was introduced.

[seonghobae]

2026-08-06 release-blocker checkpoint

PR #20 is still draft and intentionally unmerged. Its current exact head is 7a0d2f0fe4c9205db47236f28f3cdf86b29de4c0.

Current-head evidence:

• ci: success on Python 3.10, 3.11, 3.12, and 3.13
• SAST Semgrep: success
• Security Scan: success
• package build, hash-install, installed-wheel smoke, and pip check: success
• 321 tests passed
• 2,019 combined package/trust-boundary statements and 734 branches: 100%
• src/threadweave/incremental.py: 631 statements and 250 branches, both 100%
• every published GitHub code-quality review thread is resolved

The latest hardening also rejects hostile JSON container/key/scalar subclasses, cycles, and reused container identities, and enforces max_snapshot_bytes through bounded incremental UTF-8 encoding. This does not change the release sequence.

The remaining blocker is still account-side: configure the protected GitHub pypi environment and the PyPI Pending Trusted Publisher for owner ContextualWisdomLab, repository ThreadWeave, workflow release.yml, environment pypi; then dispatch the protected-main 0.2.0 release and verify provenance, SBOM attestation, tag, GitHub Release, PyPI wheel/sdist, and clean install. Do not use a long-lived token or manual upload as a bypass.

[seonghobae]

2026-08-06 release-blocker checkpoint

PR #20 remains Draft and intentionally unmerged. Its current exact head is 1f159c402484636dbaf87af707ba9560f8eba4cd.

Current-head evidence:

• ci: success on Python 3.10, 3.11, 3.12, and 3.13
• SAST Semgrep: success
• Security Scan: success
• package build, hash-install, installed-wheel smoke, and pip check: success
• 322 tests passed
• 2,038 combined package/trust-boundary statements and 748 branches: 100%
• src/threadweave/incremental.py: 650 statements and 264 branches, both 100%
• every published GitHub code-quality review thread is resolved

The latest snapshot hardening now counts UTF-8 code-point widths without calling str.encode on a complete JSON encoder chunk, so the configured byte limit does not require a second full bytes copy. This improvement does not change the release sequence.

The remaining blocker is still account-side: configure the protected GitHub pypi environment and the PyPI Pending Trusted Publisher for owner ContextualWisdomLab, repository ThreadWeave, workflow release.yml, environment pypi; then dispatch the protected-main 0.2.0 release and verify provenance, SBOM attestation, tag, GitHub Release, PyPI wheel/sdist, and clean install. Do not use a long-lived token or manual upload as a bypass.

[seonghobae]

2026-08-06 release-blocker checkpoint

PR #20 remains Draft and intentionally unmerged. Its current exact head is a38532c2b62504a2600bf0d2c8f536057b97fe01.

Current-head evidence:

• ci: success on Python 3.10, 3.11, 3.12, and 3.13
• SAST Semgrep: success
• Security Scan: success
• package build, hash-install, installed-wheel smoke, and pip check: success
• 325 tests passed
• 2,049 combined package/trust-boundary statements and 756 branches: 100%
• src/threadweave/incremental.py: 661 statements and 272 branches, both 100%
• every published GitHub code-quality review thread is resolved
• the exact-head wheel was independently installed and exercised outside the source tree

The latest hardening preflights the fixed snapshot schema and record-count bound before nested traversal, caps plain-container validation using the configured byte limit, rejects cyclic/aliased/executable JSON objects, and counts UTF-8 output without a second full bytes copy. This does not change the release sequence.

The remaining blocker is still account-side: configure the protected GitHub pypi environment and the PyPI Pending Trusted Publisher for owner ContextualWisdomLab, repository ThreadWeave, workflow release.yml, environment pypi; then dispatch the protected-main 0.2.0 release and verify provenance, SBOM attestation, tag, GitHub Release, PyPI wheel/sdist, and clean install. Do not use a long-lived token or manual upload as a bypass.