@christang/keel 5.73.0 → 5.73.1

package/assets/bootstrap/AGENTS.md

@@ -1,4 +1,4 @@
-<!-- keel:start version=5.73.0 -->
+<!-- keel:start version=5.73.1 -->
 ## Keel Bootstrap
 
 - Start every session with `keel context`; OpenSpec artifacts and Git are the only durable authority — never native memory, goals, or transcripts.

package/package.json

@@ -2,7 +2,7 @@
   "name": "@christang/keel",
   "displayName": "Keel",
   "description": "Keel OpenSpec execution discipline CLI for Claude Code, Codex, and OpenCode.",
-  "version": "5.73.0",
+  "version": "5.73.1",
   "license": "MIT",
   "repository": {
     "type": "git",

package/plugins/keel/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "keel",
-  "version": "5.73.0",
+  "version": "5.73.1",
   "description": "Keel OpenSpec execution discipline: stateless continuity, task capsules, deterministic gates, and expectation alignment for Codex and Claude Code.",
   "author": {
     "name": "TanglmChris",

package/plugins/keel/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "keel",
-  "version": "5.73.0",
+  "version": "5.73.1",
   "description": "Keel OpenSpec execution discipline: stateless continuity, task capsules, deterministic gates, and expectation alignment for Codex and Claude Code.",
   "author": {
     "name": "TanglmChris",

package/scripts/bump_version.js

@@ -165,13 +165,19 @@ function main() {
 
   prependChangelogEntry(newVersion);
 
+  // A version is released by landing its pull request: publish.yml's `land`
+  // job merges it once full-gate passes, then publishes, tags, and releases in
+  // the same run. It skips a version whose tag already exists, so a tag pushed
+  // by hand with no release means nothing publishes it at all (#162).
   process.stdout.write(
     `\nDone. Next:\n` +
-      `  1. Edit keel/CHANGELOG.md ${newVersion} entry.\n` +
+      `  1. Write the ${newVersion} entry into its stub in keel/CHANGELOG.md.\n` +
       `  2. npm test\n` +
-      `  3. git commit -am "${newVersion}"\n` +
-      `  4. git tag v${newVersion} && git push --follow-tags && git push origin v${newVersion}\n` +
-      `  5. gh release create v${newVersion} --title v${newVersion} --notes "..."\n`
+      `  3. Commit on a branch (git add -A, so an archived change is included),\n` +
+      `     push it, and open a pull request into main.\n` +
+      `  When full-gate passes, the land job merges it, publishes ${newVersion} to npm,\n` +
+      `  and creates tag v${newVersion} with its release. Do not tag by hand: the job\n` +
+      `  skips a version whose tag exists, and a pushed tag alone publishes nothing.\n`
   );
 }
 

package/scripts/validate_plugin.py

@@ -38,8 +38,8 @@ REQUIRED_SCRIPTS = [
     "scripts/validate_plugin.py",
 ]
 
-PACKAGE_VERSION = "5.73.0"
-PROTOCOL_VERSION = "5.73.0"
+PACKAGE_VERSION = "5.73.1"
+PROTOCOL_VERSION = "5.73.1"
 LEGACY_MANAGED_START = "<!-- keel:start version=2.1 -->"
 OPENSPEC_SCHEMA_NAME = "keel-spec-driven"
 # Mirrors KEEL_PACKAGE_NAME in scripts/install_to_repo.py, one of the two