pm-ops 2026.9.23 → 2026.9.26

package/CHANGELOG.md

@@ -1,5 +1,16 @@
 # Changelog
 
+## 2026.9.26 - 2026-09-26
+
+### Fixed
+
+- A publish that npm accepts late is reported as failed and the GitHub Release is skipped on bun mirror lag ([ops-ssnr](https://github.com/unbraind/pm-ops/blob/main/.agents/pm/issues/ops-ssnr.toon))
+- The guarded launcher template reads a pm-ops directory without package.json as an omit-dev install and skips the merge drivers ([ops-eyi8](https://github.com/unbraind/pm-ops/blob/main/.agents/pm/issues/ops-eyi8.toon))
+
+### Other
+
+- Certify pm CLI 2026.9.23 and adopt the guarded pm-ops merge-driver launcher ([ops-me3v](https://github.com/unbraind/pm-ops/blob/main/.agents/pm/chores/ops-me3v.toon))
+
 ## 2026.9.18 - 2026-09-18
 
 ### Added

package/README.md

@@ -306,6 +306,7 @@ Dynamic `import()` is forbidden by the fleet lint gate. Instead the template res
 
 - **pm-ops not installed** (`--omit=dev`): exits `0` after exactly one notice line
 - **pm-ops too old to export the entry, or its entry file missing**: fails the install loudly, and never skips
+- **a broken install** (`node_modules/pm-ops` left as a directory without its `package.json`, or as a dangling link): fails the install loudly; resolution fails there with the same `MODULE_NOT_FOUND` an omit-dev install produces, so the template also looks for that entry before skipping
 - **pm-ops installed**: runs `runPrepareMergeDriver` (below) and propagates its exit status
 
 Fixture tests in `test/merge-driver-launcher.test.ts` execute the shipped template against each of

package/dist/index.js

@@ -2082,7 +2082,7 @@ function renderDocstringsMarkdown(result) {
 const defineExtension = (module) => module;
 export default defineExtension({
     name: "pm-ops",
-    version: "2026.9.23",
+    version: "2026.9.26",
     activate(api) {
         if (typeof api.registerRenderer === "function") {
             // Derived from OPS_COMMAND_PATHS rather than restated. A literal copy is

package/manifest.json

@@ -1,6 +1,6 @@
 {
   "name": "pm-ops",
-  "version": "2026.9.23",
+  "version": "2026.9.26",
   "description": "Multi-repo fleet operations for pm-cli",
   "author": "@unbraind",
   "entry": "./dist/index.js",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pm-ops",
-  "version": "2026.9.23",
+  "version": "2026.9.26",
   "description": "Multi-repo fleet operations for pm-cli",
   "repository": {
     "type": "git",
@@ -121,13 +121,13 @@
     "@babel/eslint-parser": "^8.0.5",
     "@babel/plugin-syntax-typescript": "^8.0.3",
     "@types/node": "^26.2.0",
-    "@unbrained/pm-cli": "2026.9.21",
+    "@unbrained/pm-cli": "2026.9.23",
     "c8": "^12.0.0",
     "eslint": "^10.10.0",
     "fast-glob": "^3.3.3",
     "jscpd": "^5.2.1",
     "jscpd4": "npm:jscpd@4.3.0",
-    "pm-changelog": "2026.9.18"
+    "pm-changelog": "2026.9.23"
   },
   "keywords": [
     "pm-cli",

package/templates/prepare-merge-driver.ts

@@ -7,13 +7,15 @@
  * therefore imports nothing from pm-ops: it resolves the installer entry from
  * the package root and runs it in a child process. Only a missing pm-ops package skips, with one
  * notice; any other resolution failure (for example a pm-ops too old to export
- * the entry) and any installer failure fail the install.
+ * the entry, or a `pm-ops` directory whose package.json is gone) and any
+ * installer failure fail the install.
  *
  * Canonical copy: `pm-ops/templates/prepare-merge-driver.ts`. Copy it
  * unchanged to `scripts/prepare-merge-driver.ts`.
  */
 
 import { spawnSync } from "node:child_process";
+import { lstatSync } from "node:fs";
 import { createRequire } from "node:module";
 import { join } from "node:path";
 
@@ -26,12 +28,17 @@ try {
   // Only an absent pm-ops package may skip. Probing its package.json tells that
   // apart from an installed pm-ops that cannot serve the entry (exports without
   // it, no exports map, a missing file): those resolve or fail differently, and
-  // the original error is rethrown.
+  // the original error is rethrown. A probe that finds no package.json is not
+  // yet proof of absence: a broken install can leave `node_modules/pm-ops` (a
+  // directory or a dangling link) with no package.json, which fails the probe
+  // the same way, so an entry there also counts as present.
   let packagePresent = true;
   try {
     resolver.resolve("pm-ops/package.json");
   } catch (probe) {
-    packagePresent = !(probe instanceof Error && "code" in probe && probe.code === "MODULE_NOT_FOUND");
+    packagePresent =
+      !(probe instanceof Error && "code" in probe && probe.code === "MODULE_NOT_FOUND") ||
+      lstatSync(join(process.cwd(), "node_modules", "pm-ops"), { throwIfNoEntry: false }) !== undefined;
   }
   if (packagePresent) throw error;
 }