pm-github 2026.9.22 → 2026.9.26

package/CHANGELOG.md

@@ -1,5 +1,11 @@
 # Changelog
 
+## 2026.9.26 - 2026-09-26
+
+### Other
+
+- Certify pm CLI 2026.9.23 and adopt the guarded pm-ops merge-driver launcher ([pm-github-d2az](https://github.com/unbraind/pm-github/blob/main/.agents/pm/chores/pm-github-d2az.toon))
+
 ## 2026.9.22 - 2026-09-22
 
 ### Fixed

package/README.md

@@ -273,7 +273,7 @@ This package is release-ready for GitHub, npm, and Bun-compatible installs. CI r
 This repo tracks its project management in `.agents/pm/` and ships a committed `.gitattributes`
 that maps those tracker artifacts to pm-cli's field-aware Git merge drivers, so concurrent-branch
 tracker edits merge cleanly. The driver definitions live in per-clone Git config; `npm install` /
-`npm ci` wires them automatically via the `prepare` script (a portable Node guard, `scripts/prepare-merge-driver.ts`, a thin launcher over `pm-ops/merge-driver`: it runs `pm merge install` only when the `pm` CLI is on `PATH`, and no-ops cleanly when `pm` is absent. Registry installs of this package never run `prepare`; a production install of a clone (`npm ci --omit=dev`) omits `pm-ops` too, so it must pass `--ignore-scripts`; being Node-based it behaves identically on POSIX shells and Windows `cmd.exe`). To (re)run
+`npm ci` wires them automatically via the `prepare` script, `scripts/prepare-merge-driver.ts`: the launcher template pm-ops ships, copied unchanged, which a test compares byte for byte with the pinned template. It runs pm-ops's installer, which calls `pm merge install` when the `pm` CLI is on `PATH` and skips with a notice when it is not. A production install of a clone (`npm ci --omit=dev`) has no `pm-ops`, so the launcher skips with one notice, while a stale or broken `pm-ops` fails the install. Registry installs of this package never run `prepare`. Being Node-based, it behaves identically on POSIX shells and Windows `cmd.exe`. To (re)run
 manually: `npm run merge:install`.
 
 After merging a branch that touched `.agents/pm/`, reconcile any residual history-hash drift with

package/dist/index.js

@@ -3887,7 +3887,7 @@ const PROJECT_SYNC_FLAGS = [
 const defineExtension = (module) => module;
 export default defineExtension({
     name: "pm-github",
-    version: "2026.9.22",
+    version: "2026.9.26",
     activate(api) {
         // -----------------------------------------------------------------------
         // schema — declare the GitHub provenance fields so the workspace knows them

package/manifest.json

@@ -1,6 +1,6 @@
 {
   "name": "pm-github",
-  "version": "2026.9.22",
+  "version": "2026.9.26",
   "description": "GitHub Issues + Projects v2 integration. Imports issues as pm items (`pm github import`), exports pm items as GitHub issues, syncs issue state, and bidirectionally syncs pm items with a GitHub Projects v2 board (`pm github project import/sync/list/fields`) — mapping pm status to the board Status column with idempotent, no-data-loss provenance.",
   "author": "@unbraind",
   "entry": "./dist/index.js",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pm-github",
-  "version": "2026.9.22",
+  "version": "2026.9.26",
   "description": "GitHub Issues importer extension for pm-cli",
   "repository": {
     "type": "git",
@@ -44,10 +44,10 @@
     "@unbrained/pm-cli": ">=2026.8.20"
   },
   "devDependencies": {
-    "@types/node": "^26.1.1",
-    "@unbrained/pm-cli": "2026.9.21",
-    "pm-changelog": "2026.9.18",
-    "pm-ops": "2026.9.18",
+    "@types/node": "^26.6.2",
+    "@unbrained/pm-cli": "2026.9.23",
+    "pm-changelog": "2026.9.23",
+    "pm-ops": "2026.9.23",
     "typescript": "^7.0.2"
   },
   "keywords": [