Skip to content

The cross-harness, self-improving memory layer for AI agents. Join our community: https://discord.com/invite/zdNChS2fBu

fix(release): keep extension releases from taking GitHub's Latest

shukieshah7ea36e9d7666
diff --git a/.github/workflows/release-extension.yml b/.github/workflows/release-extension.yml
index b118d245..8e910b39 100644
--- a/.github/workflows/release-extension.yml
+++ b/.github/workflows/release-extension.yml
@@ -235,11 +235,14 @@ jobs:
'```' \
> /tmp/ext-release-notes.md
+ # --latest=false: GitHub's "Latest" release must stay the CLI's. The self-updater's
+ # manifest, the Linux install.sh one-liner and the update notice all resolve
+ # releases/latest, and an extension release has none of their assets.
if ! gh release view "$TAG" --repo "$REPO" >/dev/null 2>&1; then
gh release create "$TAG" --repo "$REPO" \
--title "Browser extension $TAG" \
--notes-file /tmp/ext-release-notes.md \
- --verify-tag
+ --verify-tag --latest=false
fi
gh release upload "$TAG" "$NAME" "$NAME.sha256" \
diff --git a/CLAUDE.md b/CLAUDE.md
index 3a4cdf8f..72c7073b 100644
--- a/CLAUDE.md
+++ b/CLAUDE.md
@@ -527,6 +527,12 @@ target family, and the same archive loads in Edge, Brave, Opera, Vivaldi and Arc
`ext-v*` and the CLI's `v*` trigger cannot collide: GitHub tag patterns anchor at
the start, so `v*` does not match `ext-v0.1.0`.
+The extension release is created with `--latest=false`, so GitHub's "Latest" release
+stays the CLI's. The self-updater's `update-manifest.json`, the Linux `install.sh`
+one-liner, the update notice and the README's download links all resolve
+`releases/latest`; when `ext-v0.1.0` took the label they returned 404 until
+`gh release edit <cli-tag> --latest` gave it back.
+
Bump the version in **both** `browser-extension/package.json` and
`browser-extension/src/manifest.json` before tagging. The workflow requires the
tag and both files to agree and fails otherwise.