pm-jira 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 +6 -0
- package/README.md +1 -2
- package/dist/index.js +1 -1
- package/manifest.json +1 -1
- package/package.json +4 -4
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-jira-mn9w](https://github.com/unbraind/pm-jira/blob/main/.agents/pm/chores/pm-jira-mn9w.toon))
|
|
8
|
+
|
|
3
9
|
## 2026.9.22 - 2026-09-22
|
|
4
10
|
|
|
5
11
|
### Fixed
|
package/README.md
CHANGED
|
@@ -380,8 +380,7 @@ This repo tracks its own project management in `.agents/pm/` and ships a committ
|
|
|
380
380
|
drivers, so concurrent-branch tracker edits merge cleanly instead of hard-conflicting.
|
|
381
381
|
|
|
382
382
|
The driver **definitions** live in per-clone Git config, so each clone must wire them
|
|
383
|
-
once. `npm install` / `npm ci` does this automatically via the `prepare` script
|
|
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:
|
|
383
|
+
once. `npm install` / `npm ci` does this 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 it manually:
|
|
385
384
|
|
|
386
385
|
```bash
|
|
387
386
|
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.
|
|
1728
|
+
version: "2026.9.26",
|
|
1729
1729
|
activate(api) {
|
|
1730
1730
|
// -----------------------------------------------------------------------
|
|
1731
1731
|
// schema — declare Jira provenance fields so the workspace knows them
|
package/manifest.json
CHANGED
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "pm-jira",
|
|
3
|
-
"version": "2026.9.
|
|
3
|
+
"version": "2026.9.26",
|
|
4
4
|
"description": "Jira issue sync for pm-cli",
|
|
5
5
|
"repository": {
|
|
6
6
|
"type": "git",
|
|
@@ -62,9 +62,9 @@
|
|
|
62
62
|
},
|
|
63
63
|
"devDependencies": {
|
|
64
64
|
"@types/node": "^26.1.1",
|
|
65
|
-
"@unbrained/pm-cli": "2026.9.
|
|
66
|
-
"pm-changelog": "2026.9.
|
|
67
|
-
"pm-ops": "2026.9.
|
|
65
|
+
"@unbrained/pm-cli": "2026.9.23",
|
|
66
|
+
"pm-changelog": "2026.9.23",
|
|
67
|
+
"pm-ops": "2026.9.23",
|
|
68
68
|
"typescript": "^7.0.2"
|
|
69
69
|
},
|
|
70
70
|
"keywords": [
|