Skip to content

chore(vscode): release 1.4.0 with agent 1.0.0 - #132

Merged
zy1233 merged 1 commit into
mainfrom
chore/vscode-release-1.4.0
Nov 16, 2026
Merged

zy1233 merged 1 commit into
mainfrom
chore/vscode-release-1.4.0

Conversation

@zy1233

@zy1233 zy1233 commented Nov 16, 2026

Copy link
Copy Markdown
Owner

Summary

Extension 1.4.0 bundles agent 1.0.0. There is no change in vscode/src/: the code for the max level 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.

 vscode/
 ├── package.json           version 1.2.0 -> 1.4.0, zycodeAgentVersion 0.9.1 -> 1.0.0
 ├── package-lock.json      root version -> 1.4.0
 ├── agent-assets.json      pin -> agent 1.0.0 (size + sha256 of 5 assets, python packages ==1.0.0)
 ├── CHANGELOG.md           + ## 1.4.0 (2026-11-16)
 ├── README.md              max level, Context row, "agents 0.9.1 and 1.0.0 cannot change thinking live"
 └── RELEASING.md           versions in use (1.0.0, 1.2.0, 1.4.0), next lines
 AGENTS.md                  vscode/ row: agent 1.0.0 facts
 docs/specs/                status lines of 3 notes (context usage, thinking max, extension design)

What a user of 1.2.0 gets after the update:

Thinking menu   7 levels (max, xhigh, ... off)     before: 6   (only for an agent >= 1.0.0: MAX_LEVEL_SINCE)
Context row     bar + percent + tokens             before: never shown (agent 0.9.1 sent no usage_update)
                shown for a model that has context_window; no Cost line (the agent has no price table)
Agent           0.9.1 -> 1.0.0                     compaction by the real window, stop reason max_turn_requests

Evidence

  • Before: zycodeAgentVersion 0.9.1; menu has 6 levels; Context row never shows with the bundled agent.
    After: zycodeAgentVersion 1.0.0, pin from the GitHub Release v1.0.0 (gh release view v1.0.0 --json assets); the packaging test checks that the pin, package.json and the CHANGELOG heading agree.
  • npm run check in vscode/ (typecheck, ESLint, Vitest): 323 passed, 46 skipped (the real-agent tests are off by default).
  • ruff check . and ruff format --check .: pass. No .py file changed.
  • v1.0.0 has max in ThinkingLevel (pi_agent_core/types.py) and v0.9.1 does not. So MAX_LEVEL_SINCE = "1.0.0" is right.
  • Still to run: the checks of this PR, then a dry run of vscode-extension.yml on this branch (all 5 targets, publish off). fetch-agent.mjs downloads each asset there and compares size and sha256 with the pin.
  • Not verified: the extension against agent 1.0.0 in a real VS Code window with a real provider; the max level against a real provider.

Merge Danger

Door: two-way. A merge publishes nothing. The publish is a separate manual run of vscode-extension.yml on main with a reviewer approval in the environment vscode-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 = false turns this off), and a turn that ends at max_turns has the stop reason max_turn_requests.

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.
@zy1233
zy1233 merged commit 9c24066 into main Nov 16, 2026
20 checks passed
@zy1233
zy1233 deleted the chore/vscode-release-1.4.0 branch November 16, 2026 15:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant