Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions devlog/2026-07-31_promote-stable-v1.14.8/REQ.md
Original file line number Diff line number Diff line change
@@ -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.
10 changes: 10 additions & 0 deletions devlog/2026-07-31_promote-stable-v1.14.8/WORKLOG.md
Original file line number Diff line number Diff line change
@@ -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.
Loading