pm-slack 2026.9.22 → 2026.9.26

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -1,5 +1,11 @@
1
1
  # Changelog
2
2
 
3
+ ## 2026.9.26 - 2026-09-26
4
+
5
+ ### Other
6
+
7
+ - Certify pm CLI 2026.9.23 and adopt the guarded pm-ops merge-driver launcher ([pm-slack-w4dg](https://github.com/unbraind/pm-slack/blob/main/.agents/pm/chores/pm-slack-w4dg.toon))
8
+
3
9
  ## 2026.9.22 - 2026-09-22
4
10
 
5
11
  ### Fixed
package/README.md CHANGED
@@ -371,9 +371,7 @@ This package is release-ready for GitHub, npm, and Bun-compatible installs. CI r
371
371
  This repo tracks its project management in `.agents/pm/` and ships a committed `.gitattributes`
372
372
  that maps those tracker artifacts to pm-cli's field-aware Git merge drivers, so concurrent-branch
373
373
  tracker edits merge cleanly instead of hard-conflicting. The driver **definitions** live in
374
- 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
375
- `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
376
- on POSIX shells and Windows `cmd.exe`). To (re)run manually: `npm run merge:install`.
374
+ 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`.
377
375
 
378
376
  After merging a branch that touched `.agents/pm/`, reconcile any residual history-hash drift with
379
377
  **`pm merge reconcile`** (pm-cli ≥ 2026.7.22): preview with `pm merge reconcile --dry-run`, apply with
package/dist/index.js CHANGED
@@ -1633,7 +1633,7 @@ function extractItem(ctx) {
1633
1633
  const defineExtension = (module) => module;
1634
1634
  export default defineExtension({
1635
1635
  name: "pm-slack",
1636
- version: "2026.9.22",
1636
+ version: "2026.9.26",
1637
1637
  activate(api) {
1638
1638
  // -----------------------------------------------------------------------
1639
1639
  // afterCommand hook — fires after every pm-cli command completes.
package/manifest.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "pm-slack",
3
- "version": "2026.9.22",
3
+ "version": "2026.9.26",
4
4
  "description": "Slack notifications for pm item lifecycle events",
5
5
  "author": "@unbraind",
6
6
  "entry": "./dist/index.js",
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "pm-slack",
3
- "version": "2026.9.22",
3
+ "version": "2026.9.26",
4
4
  "description": "Slack notifications for pm item lifecycle events",
5
5
  "repository": {
6
6
  "type": "git",
@@ -47,9 +47,9 @@
47
47
  },
48
48
  "devDependencies": {
49
49
  "@types/node": "^26.1.1",
50
- "@unbrained/pm-cli": "2026.9.21",
51
- "pm-changelog": "2026.9.18",
52
- "pm-ops": "2026.9.18",
50
+ "@unbrained/pm-cli": "2026.9.23",
51
+ "pm-changelog": "2026.9.23",
52
+ "pm-ops": "2026.9.23",
53
53
  "typescript": "^7.0.2"
54
54
  },
55
55
  "engines": {