@columenlabs/lumen-ship 0.1.29 → 0.1.31

package/README.md

@@ -20,7 +20,7 @@ Pin it to the same exact version as the other Lumen packages. The command needs
 
 | Command | What it does |
 |---|---|
-| `lumen-ship release` | One patch release at `main` once `cadence.every` merges landed since the newest `v*` tag, or on the first merge `cadence.days` days after it. `FORCE=1` cuts it now |
+| `lumen-ship release` | One patch release at `main` once `cadence.every` merges landed since the newest release tag, or on the first merge `cadence.days` days after it. `FORCE=1` cuts it now |
 | `lumen-ship release minor` | Tags `main` as the next minor. Its notes are the hand-written `docs/releases/v<major>.<minor>.0.md`, which must be on `main` |
 | `lumen-ship release notes` | Sets the newest minor's notes from its file again |
 | `lumen-ship release tag v1.2.3` | Makes the release of a tag that already exists (for a publish job that tags first). `REDO=1` writes its notes again |
@@ -76,6 +76,7 @@ At the repo root (or the path in `LUMEN_SHIP_CONFIG`):
   "repo": "owner/name",
   "notes": { "prompt": ".github/release-prompt.md", "model": "claude-sonnet-5-5", "maxTokens": 16000 },
   "changelog": { "path": "src/changelog.json", "apps": { "console": "console", "api": "api" } },
+  "tags": "v0.*",
   "promote": "release",
   "cadence": { "every": 10, "days": 7 }
 }
@@ -88,6 +89,7 @@ At the repo root (or the path in `LUMEN_SHIP_CONFIG`):
 | `notes.model`, `notes.maxTokens` | The model and its output limit (the model thinks first, so keep it large) |
 | `changelog.path` | Where the What's new JSON lives on `main`; left out, no changelog |
 | `changelog.apps` | Tag (lower case) → app id, for takeaways about one app |
+| `tags` | The release tags as a git glob, `v[0-9]*` by default; narrow it when older tags of another scheme sort higher |
 | `promote` | A branch fast-forwarded to each new release (a production deploy branch, say) |
 | `cadence.every`, `cadence.days` | When a patch is due. `RELEASE_EVERY` overrides `every` |
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@columenlabs/lumen-ship",
-  "version": "0.1.29",
+  "version": "0.1.31",
   "description": "Lumen's shipping kit: release notes, the What's new changelog and lint guards.",
   "license": "MIT",
   "type": "module",

package/scripts/release.sh

@@ -2,8 +2,9 @@
 # Cut a repo's GitHub releases with notes Claude writes from the merged pull requests, through the
 # GitHub REST API. Run from the repo's root, which holds lumen-ship.json (see the package README).
 #   lumen-ship release            one patch release at main once `cadence.every` first-parent merges
-#                                 landed since the latest v* tag, or on the first merge
-#                                 `cadence.days` days after it; FORCE=1 cuts it now
+#                                 landed since the latest release tag (`tags`, default v[0-9]*),
+#                                 or on the first merge `cadence.days` days after it; FORCE=1
+#                                 cuts it now
 #   lumen-ship release minor      tag main as the next minor; its notes are the hand-written
 #                                 docs/releases/v<major>.<minor>.0.md (required)
 #   lumen-ship release notes      set the latest minor release's notes from its file again
@@ -31,6 +32,8 @@ APPS=$(jq -c '.changelog.apps // {}' "$CONFIG")
 PROMOTE=$(cfg .promote)
 EVERY=${RELEASE_EVERY:-$(cfg .cadence.every)}; EVERY=${EVERY:-10}
 DAYS=$(cfg .cadence.days); DAYS=${DAYS:-7}
+# The release tags, as a git glob: narrow it when the repo keeps tags of an older scheme.
+TAGS=$(cfg .tags); TAGS=${TAGS:-v[0-9]*}
 DRY_RUN=${DRY_RUN:-0}
 FORCE=${FORCE:-0}
 REDO=${REDO:-0}
@@ -164,12 +167,12 @@ release() { # tag sha previous-tag [notes-file]: a new tag and its release
   promote "$sha"
 }
 
-LATEST=$(git tag --list 'v[0-9]*' --sort=-v:refname | head -1)
+LATEST=$(git tag --list "$TAGS" --sort=-v:refname | head -1)
 case "$MODE" in
   tag)
     TAG=${2:?usage: lumen-ship release tag v<version>}
     git rev-parse -q --verify "refs/tags/$TAG" > /dev/null || { echo "no tag $TAG" >&2; exit 1; }
-    PREV=$(git tag --list 'v[0-9]*' --sort=-v:refname | awk -v t="$TAG" 'found { print; exit } $0 == t { found = 1 }')
+    PREV=$(git tag --list "$TAGS" --sort=-v:refname | awk -v t="$TAG" 'found { print; exit } $0 == t { found = 1 }')
     SHA=$(git rev-list -n1 "$TAG")
     # A tag with no release answers 404, whose error body gh still prints: keep only an id.
     ID=$(gh api "repos/$REPO/releases/tags/$TAG" --jq .id 2> /dev/null || true)