pm-slack-standup 2026.9.23 → 2026.9.26

package/CHANGELOG.md

@@ -1,5 +1,15 @@
 # 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 ([pm-slack-standup-ykpv](https://github.com/unbraind/pm-slack-standup/blob/main/.agents/pm/issues/pm-slack-standup-ykpv.toon))
+
+### Other
+
+- Certify pm CLI 2026.9.23 and adopt the guarded pm-ops merge-driver launcher ([pm-slack-standup-19up](https://github.com/unbraind/pm-slack-standup/blob/main/.agents/pm/chores/pm-slack-standup-19up.toon))
+
 ## 2026.9.18 - 2026-09-18
 
 ### Other

package/README.md

@@ -371,10 +371,7 @@ The package and daily release workflow support npm and Bun-compatible installs.
 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 instead of hard-conflicting. 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.mjs`: it runs
-`pm merge install` only when the `pm` CLI is on `PATH`, and no-ops cleanly otherwise so
-production / `--omit=dev` installs are not broken; being Node-based it behaves identically
-on POSIX shells and Windows `cmd.exe`). To (re)run manually: `npm run merge:install`.
+per-clone Git config; `npm install` / `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
 **`pm merge reconcile`** (pm-cli ≥ 2026.7.22): preview with `pm merge reconcile --dry-run`, apply with

package/dist/index.js

@@ -2090,7 +2090,7 @@ function sharedPresentationFlags() {
 }
 export default defineExtension({
     name: "pm-slack-standup",
-    version: "2026.9.23",
+    version: "2026.9.26",
     activate(api) {
         const standupFlags = [
             { long: "--webhook", value_name: "url", description: "Slack incoming webhook URL (overrides PM_SLACK_WEBHOOK env var)" },

package/manifest.json

@@ -1,6 +1,6 @@
 {
   "name": "pm-slack-standup",
-  "version": "2026.9.23",
+  "version": "2026.9.26",
   "manifest_version": 2,
   "description": "Post pm context as a Slack standup message",
   "author": "@unbraind",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pm-slack-standup",
-  "version": "2026.9.23",
+  "version": "2026.9.26",
   "description": "Post pm context as a Slack standup message",
   "repository": {
     "type": "git",
@@ -50,12 +50,12 @@
     "@babel/eslint-parser": "^8.0.5",
     "@babel/plugin-syntax-typescript": "^8.0.3",
     "@types/node": "^26.1.1",
-    "@unbrained/pm-cli": "2026.9.21",
+    "@unbrained/pm-cli": "2026.9.23",
     "eslint": "^10.10.0",
     "fast-glob": "^3.3.3",
-    "jscpd": "^4.3.0",
-    "pm-changelog": "2026.9.18",
-    "pm-ops": "2026.9.18",
+    "jscpd": "^5.3.1",
+    "pm-changelog": "2026.9.23",
+    "pm-ops": "2026.9.23",
     "typescript": "^7.0.2"
   },
   "peerDependencies": {