Skip to content

v2026.9.25

Choose a tag to compare

@github-actions github-actions released this 25 Sep 12:50
· 311 commits to main since this release

@unbrained/pm-cli 2026.9.25

Source range: v2026.9.24...v2026.9.25

Changelog

Fixed

  • GH-1306: Isolate merge driver installation and health across Git worktrees (pm-c1dwbt)
  • GH-1305: Preserve workflow policy refusal evidence and actionable missing-field recovery (pm-o5s22y)
  • GH-1303: Canonical help and refreshable agent guidance (pm-80k965)
  • GH-1304: Deterministic release pipeline branch coverage across hosted environments (pm-m2ai6c)
  • Scheduled auto-release has a chronically high failure rate and no rolling measure, so a degraded pipeline reads as healthy one run at a time (pm-e70zh5)
  • Daily auto-release never runs in its declared window: all 84 scheduled runs fired 2.5-4 hours after the cron time, so the release clock is undocumented drift (pm-44u3wt)
  • GH-1294: release commit omits synchronized plugin runtime manifests (pm-t4prek)
  • The related ceiling is pinned to the live count with block enforcement, so recording one associative sibling relation anywhere in the tracker fails CI while the share floor it duplicates would have allowed it (pm-r3o7x4)

Security

  • Semgrep 874840452: Medium dependabot missing cooldown in .github/dependabot.yml#L3 (pm-gkut)
  • Semgrep 874840451: Medium dependabot missing cooldown in .github/dependabot.yml#L23 (pm-dmo5)

PM Tracker Evidence

Closed pm items in release window: 10
By type: Issue=10
By status: closed=10

Selected release-related tracker items:

  • pm-t4prek [Issue/closed] GH-1294: release commit omits synchronized plugin runtime manifests
  • pm-m2ai6c [Issue/closed] GH-1304: Deterministic release pipeline branch coverage across hosted environments
  • pm-e70zh5 [Issue/closed] Scheduled auto-release has a chronically high failure rate and no rolling measure, so a degraded pipeline reads as healthy one run at a time
  • pm-44u3wt [Issue/closed] Daily auto-release never runs in its declared window: all 84 scheduled runs fired 2.5-4 hours after the cron time, so the release clock is undocumented drift