v2026.5.6

@unbrained/pm-cli 2026.5.6

Source range: v2026.5.5...v2026.5.6

Changelog

Fixed

• Stabilized the linked-test timeout regression on Windows runners by keeping bounded-completion coverage while allowing slower process teardown.
• Fixed telemetry queue flushing to preserve events appended while another flush is in flight on Windows runners.

PM Tracker Evidence

Updated pm items in release window: 3
By type: Chore=1, Issue=2
By status: closed=3

Selected release-related tracker items:

• pm-0rjf [Chore/closed] Release @unbrained/pm-cli after 2026.5.4
• pm-w5j7 [Issue/closed] GitHub #20: resilient mixed-frontmatter item-format migration

v2026.5.5

@unbrained/pm-cli 2026.5.5

Source range: v2026.5.4...v2026.5.5

Changelog

Added

• Added mixed-frontmatter compatibility coverage to the release gate so previous-version json_markdown workspaces with YAML wrappers before JSON item data are migrated in a temp project before release.
• Added --repair to bundled install scripts to clear stale global pm shims before reinstalling from the npm registry.

Changed

• Hardened release post-publish verification so npm/npx/bunx checks run from a clean temp directory and fail the release workflow if package execution does not converge.
• Hardened the daily auto-release pipeline so .agents/pm-only tracker commits are ignored for publish eligibility, preventing post-release tracker closure from creating a package-only release.
• Hardened the Sentry/telemetry release gate so GitHub runners use portable token-based Sentry API checks instead of host-local wrappers, with clearer captured-output diagnostics on gate failures.
• Documented npm registry installs as the supported global update path and added recovery guidance for broken git-sourced global installs.

Fixed

• Fixed item-format migration to ignore leading YAML wrappers before JSON front matter, continue past unreadable item files with deterministic warnings, and avoid writing item_format settings before migration completes.

PM Tracker Evidence

Updated pm items in release window: 3
By type: Chore=1, Issue=2
By status: in_progress=3

Selected release-related tracker items:

• pm-0rjf [Chore/in_progress] Release @unbrained/pm-cli after 2026.5.4
• pm-w5j7 [Issue/in_progress] GitHub #20: resilient mixed-frontmatter item-format migration

v2026.5.4

@unbrained/pm-cli 2026.5.4

Source range: v2026.5.3-8...v2026.5.4

Changelog

Changed

• Relaxed release workflow npx/bunx post-publish checks to emit warnings instead of hard-failing the pipeline when registry/executor convergence lags, while keeping npm publication metadata as a blocking verification gate.

PM Tracker Evidence

No pm tracker items were updated in the selected release window.

v2026.5.3-8

@unbrained/pm-cli 2026.5.3-8

Source range: v2026.5.3-7...v2026.5.3-8

Changelog

Changed

• Updated release workflow npx verification to run the explicit package binary command (npx @unbrained/pm-cli@<version> pm --version) to avoid npm exec binary resolution drift on GitHub-hosted runners.

PM Tracker Evidence

No pm tracker items were updated in the selected release window.

v2026.5.3-7

@unbrained/pm-cli 2026.5.3-7

Source range: v2026.5.3-6...v2026.5.3-7

Changelog

Changed

• Updated release post-publish verification commands to execute the package pm binary explicitly (npm exec --package ... -- pm --version and bunx ... pm --version) and parse terminal line output robustly.

PM Tracker Evidence

No pm tracker items were updated in the selected release window.

v2026.5.3-6

@unbrained/pm-cli 2026.5.3-6

Source range: v2026.5.3-5...v2026.5.3-6

Changelog

Changed

• Added npm/npx/bunx propagation retries to release publication verification so post-publish checks wait for registry availability instead of failing immediately on transient 404 windows.

PM Tracker Evidence

No pm tracker items were updated in the selected release window.

v2026.5.3-5

@unbrained/pm-cli 2026.5.3-5

Source range: v2026.5.3-4...v2026.5.3-5

Changelog

Changed

• Hardened release workflow reliability gating so Sentry threshold checks are skipped when the runner does not provide the sentry CLI binary, preventing false-negative publish blocks on GitHub-hosted runners.

PM Tracker Evidence

No pm tracker items were updated in the selected release window.

v2026.5.3

@unbrained/pm-cli 2026.5.3

Source range: v2026.5.2...v2026.5.3

Changelog

Added

• Added progressive pm context depth, section, activity, staleness, and agenda controls so agents can request brief, standard, deep, or focused project snapshots without broad list scans.
• Added detailed CLI telemetry error classification for failed command finishes, including normalized error_code, error_category, and exit-code metadata for telemetry and local OTLP spans.
• Added regression coverage for bootstrap argument parsing, telemetry classification, Sentry helper filtering, migration gates, context output, and front-matter cache behavior.

Changed

• Decomposed src/cli/main.ts from ~5800 lines into modular command registration files: register-setup.ts, register-list-query.ts, register-mutation.ts, register-operations.ts, and shared registration-helpers.ts, reducing main.ts to ~2550 lines while preserving all command behavior and help text.
• Centralized command argument parsing and command registration helpers to reduce CLI surface drift across help, contracts, completion, and runtime telemetry paths.
• Centralized shared HTTP request handling for embeddings and vector-store providers, reducing duplicated semantic search transport logic.
• Changed the built-in telemetry capture default from max to redacted so new installs preserve agent reliability diagnostics without sending local paths or personal identifiers by default.
• Hardened CI, nightly, and release workflows around the sandboxed test harness and release readiness contracts while preserving the free GitHub Actions release path.

Fixed

• Hardened Sentry filtering so expected handled CLI usage/validation errors are logged as structured usage signals without reopening Sentry exception groups, while unexpected failures still capture normally.
• Hardened pm normalize closed-item backfill so it satisfies resolution metadata requirements without duplicating potentially sensitive close_reason text into new tracked fields.

Performance

• Added persistent on-disk front-matter cache (src/core/store/front-matter-cache.ts) for listAllFrontMatter operations, using mtime+size fingerprinting for incremental refresh and context-fingerprint-based invalidation when preferred format or schema changes. Warm list-open drops from full-scan to ~60ms for 636-item corpora.

Security

• Hardened telemetry and Sentry scrubbing so emails, private IPs, absolute local paths, bearer values, and inline credential assignments are redacted even when higher-detail telemetry capture is explicitly selected.
• Redacted sensitive infrastructure details from tracked project metadata and kept production telemetry/Sentry release audit notes in the ignored private operations area.

PM Tracker Evidence

Updated pm items in release window: 45
By type: Chore=6, Task=18, Epic=4, Feature=2, Decision=2, Issue=13
By status: in_progress=1, closed=41, open=3

Selected release-related tracker items:

• pm-0qv7 [Chore/in_progress] Release @unbrained/pm-cli after 2026.5.2
• pm-0kd4 [Task/closed] CI/CD hardening sweep - workflows + release scripts

v2026.5.2

@unbrained/pm-cli 2026.5.2

Source range: v2026.5.1-2...v2026.5.2

Changelog

Changed

• Reworked the README and public docs into progressive, agent-oriented pages with GitHub-compatible links and pm tracker cross-references.
• Hardened Sentry signal quality by suppressing expected handled PmCliError usage/validation failures while retaining unexpected exception capture.
• Added optional token-gated Sentry release and sourcemap upload to the free GitHub release workflow so published CLI stack traces can resolve source context when Sentry credentials are configured.
• Updated generated GitHub release notes so closed release-tagged pm evidence remains visible after the release item is completed.

Security

• Kept private operations material out of public docs and package output; local production operations artifacts remain ignored by git.

PM Tracker Evidence

Updated pm items in release window: 81
By type: Chore=10, Epic=8, Decision=3, Feature=20, Issue=22, Task=18
By status: closed=78, open=3

Selected release-related tracker items:

• pm-5jw8 [Chore/closed] Release @unbrained/pm-cli 2026.5.2
• pm-q71q [Issue/closed] Pin release dependency ranges for Dependabot hygiene

v2026.5.1-2

@unbrained/pm-cli 2026.5.1-2

Source range: v2026.5.1...v2026.5.1-2

Changelog

Fixed

• Pinned direct runtime and development dependency ranges instead of publishing latest specifiers, including undici@^8.1.0, so installs are deterministic and GitHub Dependabot evaluates the manifest against a non-vulnerable patched range.

PM Tracker Evidence

Updated pm items in release window: 3
By type: Issue=2, Chore=1
By status: in_progress=1, closed=2

Selected release-related tracker items:

• pm-q71q [Issue/in_progress] Pin release dependency ranges for Dependabot hygiene