Repository navigation
chore(release): prepare 0.7.0 - versions, extension floors, changelog - #55
Merged
Merged
Conversation
Core, harness and cli go from 0.6.0 to 0.7.0. They pin each other with ==. The two TUI crates that zypi shows (pi-pager-bin, pi-version) and tui/Cargo.lock carry the same version (scripts/tests/test_release_versions.py). The extension packages are released with the core, so all four need pi-agent-core-lc>=0.7.0 (pi_agent_core/tests/test_extension_packaging.py), and pi-dynamic-workflows-py also needs pi-agent-harness-lc>=0.7.0. The publish step skips a version that is on PyPI already, so they get new versions: web-access, goal-x and dynamic-workflows 0.3.0 -> 0.4.0, pi-mcp 0.1.0 -> 0.2.0. The README of pi-mcp-py (its PyPI page) names the new floor. CHANGELOG.md: [Unreleased] becomes [0.7.0] - 2026-10-30. It gets an opening paragraph (the release page shows it first), entries for the site (#50 to #54), the PyPI Website link, the queue cleanup fix (#47) and the new version numbers, and the known issues of 0.6.0 that still hold. The one about F7-02 to F7-09 is gone: the fixes are in this release. Why now: the published 0.6.0 has no `--setup` and no `pi-agent-cli-lc` console script, but the site and the README on main describe both.
…cript is described The CHANGELOG entry for the console script said that it reaches PyPI with the next release. In the 0.7.0 section, which is the text of the release page, that reads as 0.8.0. The README of pi-agent-cli-lc (its PyPI page) said "from the release after 0.6.0". Both name 0.7.0 now.
Merged
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.
Summary
Release prep for v0.7.0, in the shape of #39 (0.6.0): versions, extension floors, changelog. No code.
CHANGELOG.md:[Unreleased]becomes[0.7.0] - 2026-10-30.Evidence
--setupand nopi-agent-cli-lcscript, but the site and the README onmaindescribe both. A tag onmainwould build 0.6.0 files,skip-existingwould upload nothing, and the release page would be empty (no[0.7.0]section for theawkinrelease.yml).After:
test_release_versions.py,test_extension_packaging.pyandtest_agent_info.py: 18 passed (Windows).ruff checkandruff format --check: clean. The release body, cut with theawkofrelease.yml: 22,324 characters, with the sections Added, Changed, Fixed and Known issues. Dry run ofReleaseon this branch (publishes nothing): https://github.com/zy1233/pi-python/actions/runs/41037156832Merge Danger
Door: two-way for this PR. One-way for the tag
v0.7.0that comes after it: PyPI never takes the same version twice.Blast Radius: PyPI
The tag starts
release.yml: tests, 7 packages to PyPI, the Linux and macOS binaries, the GitHub Release. Put the tag on the merge commit of this PR.actions/download-artifact@v7runs only in the two publish jobs, so the dry run does not test it (see the CHANGELOG, "Changed"). If it fails, nothing is published, and a re-run of the job is safe (skip-existing: true).