From 24907b0759284be62f8284cc1571df23e5b0fb14 Mon Sep 17 00:00:00 2001 From: ranxianglei Date: Fri, 31 Jul 2026 15:04:28 +0800 Subject: [PATCH] =?UTF-8?q?promote:=20stable=20v1.14.8=20=E2=80=94=20stabl?= =?UTF-8?q?e=20tag=20update?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- devlog/2026-07-31_promote-stable-v1.14.8/REQ.md | 10 ++++++++++ devlog/2026-07-31_promote-stable-v1.14.8/WORKLOG.md | 10 ++++++++++ 2 files changed, 20 insertions(+) create mode 100644 devlog/2026-07-31_promote-stable-v1.14.8/REQ.md create mode 100644 devlog/2026-07-31_promote-stable-v1.14.8/WORKLOG.md diff --git a/devlog/2026-07-31_promote-stable-v1.14.8/REQ.md b/devlog/2026-07-31_promote-stable-v1.14.8/REQ.md new file mode 100644 index 0000000..b66c8e0 --- /dev/null +++ b/devlog/2026-07-31_promote-stable-v1.14.8/REQ.md @@ -0,0 +1,10 @@ +# REQ: Promote v1.14.8 to npm `stable` tag + +## Problem +npm `stable` tag is still at `1.14.7` while `latest` is at `1.14.8`. Users installing via `opencode-acp@stable` get the old version. + +## Solution +Create a promote-stable PR. On merge, CI runs `npm dist-tag add opencode-acp@1.14.8 stable`. + +## Rationale +v1.14.8 has been on `latest` since 2026-07-30 and validated in production. Promoting to `stable` makes it available to conservative users. diff --git a/devlog/2026-07-31_promote-stable-v1.14.8/WORKLOG.md b/devlog/2026-07-31_promote-stable-v1.14.8/WORKLOG.md new file mode 100644 index 0000000..ebe5e06 --- /dev/null +++ b/devlog/2026-07-31_promote-stable-v1.14.8/WORKLOG.md @@ -0,0 +1,10 @@ +# WORKLOG: Promote v1.14.8 to npm `stable` tag + +## Steps +1. Created branch `2026-07-31_promote-stable-v1.14.8` from master (`e637f57`) +2. Created devlog REQ.md +3. Commit message: `promote: stable v1.14.8 — stable tag update` +4. On merge, CI detects promote-stable pattern → runs `npm dist-tag add opencode-acp@1.14.8 stable` + +## No code changes +This is a tag promotion only. No source code, tests, or version numbers modified.