pm-github 2026.10.23 → 2026.10.24

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.10.24 - 2026-10-24
4
+
5
+ ### Fixed
6
+
7
+ - Publish tracker sync after restoring workflow-owned setup artifacts ([pm-github-sync-setup-artifacts](https://github.com/unbraind/pm-github/blob/main/.agents/pm/issues/pm-github-sync-setup-artifacts.toon))
8
+
3
9
  ## 2026.10.23 - 2026-10-23
4
10
 
5
11
  ### Added
package/README.md CHANGED
@@ -839,6 +839,8 @@ Fleet repos sync their issues into pm through ONE audited implementation: the re
839
839
 
840
840
  When the tracker has no changes, regenerated `CHANGELOG.md` drift is discarded and the run emits a notice that the caller's own `changelog:check` owns that drift. The sync closes any owned open review PR and exits successfully without pushing or dispatching CI. Changelog changes are published only together with tracker changes.
841
841
 
842
+ Before extension and attributes setup, both reusable maintenance workflows require `.gitattributes` and the tracker’s `extensions/.managed-extensions.json` to match the checkout, including the index and ignored untracked files. Immediately after setup they save the runtime artifacts outside the checkout, then restore original tracked bytes or remove setup-created files before any privacy or publication scan. Strict health temporarily uses the saved runtime files after checking that both paths still match the baseline; an exit trap restores the baseline even when health fails. No caller script runs inside either setup window. Preexisting edits and later caller edits to either artifact fail closed and remain untouched, including ignored files. The publication allowlist stays unchanged. Callers receive the fix through their Dependabot workflow pins.
843
+
842
844
  The explicit allowed scope for changed paths is:
843
845
 
844
846
  - Files beneath the SDK-resolved repository-local pm tracker, excluding its `extensions/`, `locks/`, and `checkpoints/` runtime directories. The extension setup files `settings.json` and `history/_workspace.jsonl` are permitted during setup, then restored before publication and excluded from both the scan and commit.
package/dist/index.js CHANGED
@@ -5307,7 +5307,7 @@ const PROJECT_SYNC_FLAGS = [
5307
5307
  const defineExtension = (module) => module;
5308
5308
  export default defineExtension({
5309
5309
  name: "pm-github",
5310
- version: "2026.10.23",
5310
+ version: "2026.10.24",
5311
5311
  activate(api) {
5312
5312
  // -----------------------------------------------------------------------
5313
5313
  // schema — declare the GitHub provenance fields so the workspace knows them
package/manifest.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "pm-github",
3
- "version": "2026.10.23",
3
+ "version": "2026.10.24",
4
4
  "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.",
5
5
  "author": "@unbraind",
6
6
  "entry": "./dist/index.js",
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "pm-github",
3
- "version": "2026.10.23",
3
+ "version": "2026.10.24",
4
4
  "description": "GitHub Issues importer extension for pm-cli",
5
5
  "repository": {
6
6
  "type": "git",