promote: stable v1.14.26 — sync stable tag with latest (1.14.19 → 1.14.26)

[ranxianglei]

Promotes opencode-acp@1.14.26 (current npm latest) to the npm stable dist-tag.

Why

• npm stable still points at 1.14.19 (promoted 2026-08-15 via promote: stable v1.14.19 — pipeline-fixed release incl. 14.14/14.16 content #309) — 7 versions behind latest (1.14.26, published 2026-08-29).
• Users installing opencode plugin opencode-acp@stable --global get 1.14.19 and miss every fix/feature since.

What's included in stable 1.14.19 → 1.14.26

Version	Highlights
v1.14.20 (#316)	post-v1.14.19 fix batch (modelContextLimit, inactive-block decompress, logging)
v1.14.21 (#317)	/acp command fixes & completion (permission gate, export, help)
v1.14.22 (#323)	stable system-prompt token estimate (#255)
v1.14.23 (#331)	fix batch (#325 #326 #327 #328)
v1.14.24 (#333)	decision-level logging enabled by default
v1.14.25 (#336)	self-disable under billion-context proxy
v1.14.26 (#353)	per-provider/per-model compress.providers overrides (#351); growth nudge floor minNudgeContextPercent (#343)

Why not cut v1.14.27

Master HEAD (ba5ef36) differs from tag v1.14.26 only by PR #352 (soft-deprecation docs + 11 lines in lib/config.ts, no behavior change). No new code justifies a fresh release number; v1.14.26 has already run as latest for ~5 days.

How it works

No code change (devlog only). On merge, release.yml detects the promote-stable pattern (squash title promote: stable v1.14.26 — ..., or standard merge of branch ..._promote-stable-v1.14.26) and runs npm dist-tag add opencode-acp@1.14.26 stable. Both squash and merge-commit merge styles trigger it.

Verification

• npm view opencode-acp dist-tags → latest: 1.14.26 (published 2026-08-29T05:53Z), stable: 1.14.19
• master HEAD ba5ef36 = tag v1.14.26 + PR docs(deprecate): mark minContextLimit + modelMinLimits deprecated #352 docs only
• ./scripts/ci/check-pr.sh 2026-09-03_promote-stable-v1.14.26 origin/master — all checks passed (branch name, devlog REQ/WORKLOG, version unchanged)

After merge

Verify with npm view opencode-acp dist-tags → stable: 1.14.26.

Known risks (out of scope here)

#346/#347 (resume context-overflow loop) are being fixed by open PRs #348/#349/#350. Those bugs affect current stable and latest users equally — promoting introduces no new regression risk.

[github-actions]

📦 Built Plugin Artifact

Branch: 2026-09-03_promote-stable-v1.14.26 (dda54d7)

Option A — Install from npm PR tag (recommended)

opencode plugin opencode-acp@pr-358 --global

Each push to this PR publishes a new version under the pr-358 npm tag.

Option B — Install from GitHub

opencode plugin "github:ranxianglei/opencode-acp#2026-09-03_promote-stable-v1.14.26" --global

Option C — Download artifact

1. Download the artifact from the Actions run
2. Extract the tarball and install:

tar xzf opencode-acp-pr358.tgz
cp -r package/dist ~/.cache/opencode/packages/opencode-acp@latest/node_modules/opencode-acp/dist

3. Restart opencode to pick up changes.

---

This comment is automatically updated on each push.

[ranxianglei]

🤖 ework agent · qwen3.8-27b

[bot] 🏷 Picked up. Initial findings:

• PR promote: stable v1.14.26 — sync stable tag with latest (1.14.19 → 1.14.26) #358 already exists on GitHub (open, head ranxianglei:2026-09-03_promote-stable-v1.14.26, single commit dda54d7 adding only devlog/2026-09-03_promote-stable-v1.14.26/{REQ,WORKLOG}.md — no code, no version bump). So this thread tracks that PR; nothing left to create.
• Verified npm view opencode-acp dist-tags: latest: 1.14.26, stable: 1.14.19 ✓
• Verified git diff --stat v1.14.26 origin/master: only PR docs(deprecate): mark minContextLimit + modelMinLimits deprecated #352 content (docs ×4, dcp.schema.json, devlog REQ/WORKLOG, lib/config.ts +11) — matches the "no new code" claim.

Now doing full triage: release.yml promote-stable detection (squash + merge-commit paths), check-pr.sh re-run, devlog content review, PR CI status, and duplicate screening. Will follow up with conclusions.

[ranxianglei]

🤖 ework agent · qwen3.8-27b

[bot] 🏷 Triage complete — PR verified, ready to merge once e2e goes green.

Duplicate screening

No duplicates. Searched open+closed issues for similar promotion requests — none. Prior promotions (#270/#273/#283/#309) are distinct per-version items. This thread mirrors GitHub PR #358, whose origin request is #356 ("发布一个 stable 版本 pr") — already cross-referenced in the branch's REQ.md. After merge, #356 can be closed as fulfilled.

What I verified (all claims in the OP hold up)

Claim	Evidence
stable stale at 1.14.19	npm view opencode-acp dist-tags → latest: 1.14.26, stable: 1.14.19 ✓
master = v1.14.26 + docs only	git diff --stat v1.14.26 origin/master: 8 files, all from merged PR #352. Inspected the two non-markdown ones: lib/config.ts +11 = JSDoc @deprecated comments on minContextLimit/modelMinLimits; dcp.schema.json = description strings only. Zero behavior change. ✓
No code / no version bump	Branch dda54d7 contains exactly devlog/2026-09-03_promote-stable-v1.14.26/{REQ,WORKLOG}.md (48 insertions); package.json untouched (still 1.14.26) ✓
Mechanism works for both merge styles	Read .github/workflows/release.yml: Pattern 3 (^promote: stable v…) matches the squash title; Pattern 4 (.*promote-stable-v…) matches a standard merge of the branch name. Version extraction uses grep -oE 'v[0-9]+\.[0-9]+\.[0-9]+' | head -1, so the (1.14.19 → 1.14.26) in the title can't be mis-picked (no literal v prefix). Runs npm dist-tag add opencode-acp@1.14.26 stable with NPM_TOKEN, then comments the result back on the PR. Rebase style also matches Pattern 3 ✓
check-pr.sh passes	Re-ran locally from a worktree checked out at dda54d7: branch name ✓, devlog REQ+WORKLOG ✓, version unchanged ✓. (Note: running it from any other checkout false-fails the devlog check — the script tests cwd, not the branch ref.)
Devlog quality	REQ.md: goal/context/mechanism/risk sections accurate and consistent with repo history; WORKLOG.md records the verification steps. Compliant with §5.1.2 ✓

Review requirements

§5.3 dual-agent review applies to changes under lib/ — this PR has none, so it doesn't apply. Same for test review (§5.6).

Current CI (head dda54d7)

pr-validation ✓ · build ✓ · test (22) ✓ · test (24) ✓ · build-artifact ✓ · e2e still in_progress → mergeable_state: blocked solely because of the pending e2e run.

Conclusion & next step

The promotion is sound: stable is genuinely 7 versions behind, v1.14.26 has ~5 days as latest, no new code justifies v1.14.27, and the known risks (#346/#347, fixed by open #348/#349/#350) affect stable and latest users equally — no new regression introduced.

Per AGENTS.md §5.1.1.2, merging is a human-only operation — I won't merge. Once e2e turns green, please merge on the PR page (squash or standard merge both trigger the promote correctly). Then verify: npm view opencode-acp dist-tags → stable: 1.14.26, and close #356.

[github-actions]

✅ Promoted opencode-acp@1.14.26 to npm stable tag.

opencode plugin opencode-acp@stable --global