Repository navigation
chore(vscode): release 1.4.0 with agent 1.0.0 - #132
Merged
Merged
Conversation
Move the agent pin from 0.9.1 to 1.0.0 (size and sha256 of the five release assets). The Thinking menu now has max for an agent of 1.0.0 or later, and the Context row shows for a model that has context_window. Update the README, the CHANGELOG, the design notes and AGENTS.md to match.
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
Extension 1.4.0 bundles agent 1.0.0. There is no change in
vscode/src/: the code for themaxlevel and the Context row was merged in #131. This PR moves the pin, bumps the version, and makes the docs say what is now true.What a user of 1.2.0 gets after the update:
Evidence
zycodeAgentVersion0.9.1; menu has 6 levels; Context row never shows with the bundled agent.After:
zycodeAgentVersion1.0.0, pin from the GitHub Releasev1.0.0(gh release view v1.0.0 --json assets); the packaging test checks that the pin,package.jsonand the CHANGELOG heading agree.npm run checkinvscode/(typecheck, ESLint, Vitest): 323 passed, 46 skipped (the real-agent tests are off by default).ruff check .andruff format --check .: pass. No.pyfile changed.v1.0.0hasmaxinThinkingLevel(pi_agent_core/types.py) andv0.9.1does not. SoMAX_LEVEL_SINCE = "1.0.0"is right.vscode-extension.ymlon this branch (all 5 targets,publishoff).fetch-agent.mjsdownloads each asset there and compares size and sha256 with the pin.maxlevel against a real provider.Merge Danger
Door: two-way. A merge publishes nothing. The publish is a separate manual run of
vscode-extension.ymlonmainwith a reviewer approval in the environmentvscode-publish.A published version cannot be changed or published again. If 1.4.0 is wrong, the fix is 1.4.1.
Blast Radius: extension-users
After the publish, a user of 1.2.0 gets a new agent binary (1.0.0) with the update. Two agent changes reach the user: the agent compacts a long chat by itself when the model has
context_window(auto_compact = falseturns this off), and a turn that ends atmax_turnshas the stop reasonmax_turn_requests.