@eclipse-docks/cli 0.7.130 → 0.7.132

package/README.md

@@ -23,6 +23,9 @@ to `origin` first. The tag message body becomes the GitHub Release notes.
 Wire release in CI with [`.github/workflows/app-release.yml`](../../.github/workflows/app-release.yml):
 downstream apps usually trigger it on `v*` tag push; this monorepo waits for a green
 **CI** run on `main` first (see [`.github/workflows/release.yml`](../../.github/workflows/release.yml)).
+If CI fails after the tag was pushed, that workflow deletes the orphan remote tag so
+GitHub Release history has no gaps. Remove the local tag before retrying:
+`git tag -d vX.Y.Z`.
 
 The last version is the most recent `vX.Y.Z` tag reachable from `HEAD` (via
 `git describe`), not the highest semver tag in the repository. That drives the

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@eclipse-docks/cli",
-  "version": "0.7.130",
+  "version": "0.7.132",
   "description": "Developer CLI for Eclipse Docks apps (release automation and more)",
   "type": "module",
   "bin": {

package/src/commands/release.js

@@ -220,6 +220,8 @@ export async function release(argv, cwd = process.cwd()) {
   if (opts.push) {
     git(['push', 'origin', version], cwd);
     console.log(`\nPushed tag ${version}. Release runs after CI succeeds on main.`);
+    console.log('If CI fails, the remote tag is removed automatically; delete your local tag before retrying:');
+    console.log(`  git tag -d ${version}`);
   } else {
     console.log(`\nCreated annotated tag ${version}. Push your branch and tag to trigger the release:`);
     const branch = currentBranch(cwd);