Repository navigation
feat: 1.0.0 - zypi starts zycode-agent, --setup, standalone bundles, Linux aarch64 TUI - #130
Merged
Merged
Conversation
…the known issues to 1.0.0 The merge of the 1.0.0 branch had dropped the heading of 0.9.1, so the release notes of v1.0.0 (cut by awk from one heading to the next) would have held the text of 0.9.1. Also: the 1.0.0 section now lists usage_update, the max thinking level, auto_compact and max_turn_requests (all from #131), moves the removal of the Python fallback of zypi to Changed as a behaviour change with the one-line fix, says what the Omarchy item really is (a draft with two known defects), and has its own Known issues. Date 2026-11-16.
…, show 1.0.0 as stable zypi no longer starts python -m pi_agent_cli when nothing is set, and the pip package has no zycode-agent command. The install steps on the web site (en and zh), in the README and in the TUI guide still told a user to pip install the agent and download a bare zypi, which fails at the first start. They now use the bundle (zypi and zycode-agent in one archive), and say how to use the pip package (PI_PYTHON). The bundle URLs name the tag (releases/download/v1.0.0/...) and not latest: the file name holds the version, so latest would give a 404 after the next release. The version for the web text is one constant in web/src/data/site.ts. The hero badge and the terminal tag said beta while the page says 1.0.0 is stable and the README table says Stable. The docs that still described the old default (DESIGN, WINDOWS, the pager user guide, tui/NOTICE) say zycode-agent now. The Omarchy design record is marked as a draft with its two known defects.
…ndling with real archives The publish step of Agent binaries ignored a failed download (|| true) and skipped a target whose input was missing, so a release could go out with a green run and no bundle, while the README and the web page link to the bundles. It now fails for a missing zypi file, a missing agent archive or a bundle that is not made, attaches the agent archives first (the VS Code extension needs them), and checks that the release holds the three bundles at the end. A tag from before the bundles (its build.py has no --bundle-from-archive) still gets its agent archives and no bundle, so the repair path of old tags works. Checked in WSL with a stand-in gh for five cases (all there, no zypi file, no agent archive, old build.py, an upload that loses a bundle). build.py: the check for src is None could not run, because with None raises first (TypeError). Only a regular file counts as the program now, and a directory of that name gives the clear FileNotFoundError. The tests now go through the real pack(), cover the zip archive, the two error cases and the command line that the workflow runs.
…fier The 1.0.0 entry said that all seven Python packages get Development Status :: 5 - Production/Stable. Only three have that classifier (pi-agent-core-lc, pi-agent-harness-lc, pi-agent-cli-lc). The four extension packages never had a Development Status classifier. Found when the seven wheels of the Release dry run were installed in a clean venv.
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
zypistartszycode-agentand has--setup. Each tag gets standalone bundles (zypiandzycode-agentin one archive) for Linux x86_64, Linux aarch64 and macOS arm64. All seven Python packages and the TUI go to 1.0.0. The #131 changes (usage_update, themaxthinking level,auto_compact, the stop reasonmax_turn_requests) ship in the same release.Changes after review
A review of this PR found two high and several medium and low problems. All are fixed on this branch:
The omarchy patch in
docs/specs/2026-11-15-omarchy-agent-pr.mdis a draft. Its status line names two defects that are not fixed here (see Known issues in the CHANGELOG). It is not part of this release.Evidence
pytest6238 passed, 107 skipped. Linux (WSL, clean venv fromgit archive): 6303 passed, 42 skipped.checkandformat --checkpass with 0.16.0 (the pin ofrelease.yml) and 0.17.5.npm run checkandnpm run buildpass. The built pages name the tag-pinned URL and no longer say "beta".agent-binaries.yml, run in WSL with a stand-ingh, 5 cases: all three bundles; a missingzypi-*asset; a missing agent archive; an old tag whosebuild.pyhas no--bundle-from-archive;build.pythat makes no file. The first and the fourth pass, the other three stop with::error::.workflow_dispatchon this branch, run 43841723521): all jobs passed:Pre-release tests,Build Python packages, and the three TUI builds (Linux x86_64, Linux aarch64 - the first run of the new job - and macOS arm64).Publish to PyPIandGitHub Releasewere skipped, as a dry run does.uv pip checkis clean, all seven import.pi-agent-cli-lchas the console scriptspi-agent-cliandpi-agent-cli-lc(nozycode-agent, as the docs say).Not verified:
zypifor Linux aarch64 and macOS arm64 was built by CI but nobody ran it by hand;maxwas not sent to a real provider; themaxitem of the VS Code menu was not tried in a real window.Merge Danger
Door: one-way
Merge to
maindeployszycode.devat once (web/changes). The README and the site name thev1.0.0bundles, and these files exist only after theReleaseworkflow and thenAgent binarieshave run on the tag. Tagv1.0.0right after the merge. The tag publishes the seven packages to PyPI, and PyPI never takes a version back.Blast Radius: release