Conversation
RULED openxFactory#656 comment 5963162921 (Brett Heap, 2026-10-02): "0.1.0 (Recommended)". openDox's first public PyPI release carries version 0.1.0: the first public release, with the API still pre-1.0. This bump is the last phase-3 openDox-code landing. The openDox root then pins this commit (T087), and the release workflow (openDox-code#78) publishes only the commit the root's contracts/code-pin.yaml names, at the cut, after T089. Nothing else in pyproject.toml moves here; its readme line rides in #78. Arc: neutral-product-standalone-operability Lane: openxfactory-4 (openXfactory-4-openDox_extraction) Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
There was a problem hiding this comment.
Copilot review overview
🟢 Approval recommended
The focused metadata change is valid and consistent with the documented release plan.
Review effort: Balanced
Findings: None
What changed in this PR
Bumps the opendox package to its first public pre-1.0 release version.
Changes:
- Sets project version to
0.1.0. - Documents the coordinated release and root-pin sequence.
| File | Description |
|---|---|
pyproject.toml |
Updates package version metadata and release context. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Arc: neutral-product-standalone-operability Lane: openxfactory-4 (openXfactory-4-openDox_extraction) Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Arc: neutral-product-standalone-operability Lane: openxfactory-4 (openXfactory-4-openDox_extraction) Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
|
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.



Lane: openxfactory-4 (openXfactory-4-openDox_extraction)
Arc: neutral-product-standalone-operability
T099's release step:
pyproject.toml'sversiongoes from0.0.0to0.1.0. This is RULED5963162921(Brett Heap, 2026-10-02): "0.1.0 (Recommended)". openDox's first public PyPI release (T099, RULED5962754358item 1) carries version 0.1.0, as the first public release, with the API still pre-1.0.It is the last phase-3 openDox-code landing. The order, as
5963162921sets it:release.ymlis dispatched withversion=0.1.0. It publishes only the commit the root'scontracts/code-pin.yamlnames, and refuses any other.DRAFT, after T063. The holder posts READY, and the landers merge.
readme = "README.md"rides in DRAFT (phase 3, after T063): T099, publish openDox to PyPI by trusted publishing (10.3's install line) #78, not here.7ee2b425with this head31361c91auto-mergedpyproject.toml. The[project]table then readsversion = "0.1.0"and keeps DRAFT (phase 3, after T063): T099, publish openDox to PyPI by trusted publishing (10.3's install line) #78'sreadmeline.0.0.0appears elsewhere only as the runtime container image's placeholder tag (deploy/kubernetes/, held bytests_runtime/test_deploy_shape.py), which is a separate value and does not move.The refresh of 2026-10-04:
mainca9e1bd5merged, the head is31361c91This PR stays DRAFT, and it lands last. The refresh leaves only a final
mainmerge for later.mainwas merged twice:c4b55cc4(T073, 13.4a — /capabilities gains an install block, read from the serving process's own settings (plan 034) #72, T084, 4.3: the last deferred reaches through declared seams; consumer_reach retired (plan 034) #77, T103, every loopback route checks the Host (DNS rebinding) (plan 034) #80, T102, the staging workbench offers the editors and the chat rail by scope (plan 034) #81, T102 follow-on: the chat rail reads a thread only with a branch session (plan 034) #85), thenca9e1bd5(T082, 16.5: every other surface works with no model (plan 034) #76). Both merges were clean. Againstmain, this PR's diff is stillpyproject.tomlalone: the version line and its comment.31361c91, in a venv with thetestextra, the bundled PostgreSQL included:tests/:3178 passed, 11 skipped;tests_runtime/:632 passed, 166 skipped.buildjob ran on DRAFT (phase 3, after T063): T099, publish openDox to PyPI by trusted publishing (10.3's install line) #78's head merged with this head, soversion = "0.1.0"comes from here. It passed every run step: the version gate,twine check --strict, every artifact check, and the fresh-venv install and run. The wheel built wasopendox-0.1.0-py3-none-any.whl. DRAFT (phase 3, after T063): T099, publish openDox to PyPI by trusted publishing (10.3's install line) #78's body has the details.🤖 Generated with Claude Code