pm-jira 2026.9.18 → 2026.9.22

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,15 @@
1
1
  # Changelog
2
2
 
3
+ ## 2026.9.22 - 2026-09-22
4
+
5
+ ### Fixed
6
+
7
+ - A publish that npm accepts late is reported as failed and the GitHub Release is skipped on bun mirror lag ([pm-jira-9b9k](https://github.com/unbraind/pm-jira/blob/main/.agents/pm/issues/pm-jira-9b9k.toon))
8
+
9
+ ### Other
10
+
11
+ - Certify pm CLI 2026.9.21 and install merge drivers through the canonical pm-ops launcher ([pm-jira-jrkg](https://github.com/unbraind/pm-jira/blob/main/.agents/pm/tasks/pm-jira-jrkg.toon))
12
+
3
13
  ## 2026.9.18 - 2026-09-18
4
14
 
5
15
  ### Other
package/README.md CHANGED
@@ -381,7 +381,7 @@ drivers, so concurrent-branch tracker edits merge cleanly instead of hard-confli
381
381
 
382
382
  The driver **definitions** live in per-clone Git config, so each clone must wire them
383
383
  once. `npm install` / `npm ci` does this automatically via the `prepare` script
384
- (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 it manually:
384
+ (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 it manually:
385
385
 
386
386
  ```bash
387
387
  npm run merge:install # or: pm merge install
package/dist/index.js CHANGED
@@ -1725,7 +1725,7 @@ const VALIDATE_FLAGS = [
1725
1725
  const defineExtension = (module) => module;
1726
1726
  export default defineExtension({
1727
1727
  name: "pm-jira",
1728
- version: "2026.9.18",
1728
+ version: "2026.9.22",
1729
1729
  activate(api) {
1730
1730
  // -----------------------------------------------------------------------
1731
1731
  // schema — declare Jira provenance fields so the workspace knows them
package/manifest.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "pm-jira",
3
- "version": "2026.9.18",
3
+ "version": "2026.9.22",
4
4
  "description": "Jira issue sync for pm-cli",
5
5
  "author": "@unbraind",
6
6
  "entry": "./dist/index.js",
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "pm-jira",
3
- "version": "2026.9.18",
3
+ "version": "2026.9.22",
4
4
  "description": "Jira issue sync for pm-cli",
5
5
  "repository": {
6
6
  "type": "git",
@@ -22,7 +22,7 @@
22
22
  "scripts": {
23
23
  "build": "tsc",
24
24
  "build:test": "tsc -p tsconfig.test.json",
25
- "prepare": "node scripts/prepare-merge-driver.mjs",
25
+ "prepare": "node scripts/prepare-merge-driver.ts",
26
26
  "merge:install": "pm merge install",
27
27
  "test": "npm run build && npm run build:test && node --test test/*.test.ts",
28
28
  "dev": "tsc --watch",
@@ -62,9 +62,9 @@
62
62
  },
63
63
  "devDependencies": {
64
64
  "@types/node": "^26.1.1",
65
- "@unbrained/pm-cli": "2026.9.17",
66
- "pm-changelog": "2026.9.16",
67
- "pm-ops": "2026.9.13",
65
+ "@unbrained/pm-cli": "2026.9.21",
66
+ "pm-changelog": "2026.9.18",
67
+ "pm-ops": "2026.9.18",
68
68
  "typescript": "^7.0.2"
69
69
  },
70
70
  "keywords": [