Skip to content

v2026.6.7

Choose a tag to compare

@github-actions github-actions released this 07 Jun 07:09
· 62 commits to main since this release

@unbrained/pm-cli 2026.6.7

Source range: v2026.6.6...v2026.6.7

Changelog

Added

  • pm-governance-audit: onWrite/onRead hooks exemplar (hooks capability) (pm-7m8p)
  • pm history-compact: checkpoint-based history stream compaction (pm-3pbq)
  • Advanced relevance tuning (post-v0.1): cross-encoder reranking + query expansion (pm-7tsx)
  • Configurable vector store collection name (post-v0.1 adapter optimization) (pm-usw2)
  • pm copy <id>: clone an item to a new ID with optional title override (pm-m4nn)
  • pm aggregate --sum/--avg: numeric aggregation over filtered items (pm-bvns)
  • pm list --tree: recursive subtree rendering with indented hierarchy (pm-vbzc)
  • Configurable semantic corpus character limit (search.embedding_corpus_max_characters) (pm-cxdg)
  • Per-query hybrid weight override: pm search --semantic-weight (post-v0.1) (pm-cy8i)

Fixed

  • Track removal of TOON upstream bracket-bug workaround when upstream fix ships (pm-idnz)
  • Drift-scan cache can false-hit on mtime-preserving file copies (pm-up22)
  • Search relevance evaluation harness (golden queries, nDCG) for regression detection (pm-22x2)

Security

  • Harden afterCommand coverage and GitHub code-scanning visibility (pm-izid)

Other

  • Agent command compatibility and package command discovery (pm-7etc)
  • Package install fallback hints and extension collision plans (pm-e48i)
  • Stabilize npx onboarding path for scoped pm package (pm-pgew)
  • Publish pm-github starter package as a community reference (credential-requiring pattern) (pm-zw0n)
  • Make list --ids repeatable for focused agent working-set refresh (pm-42tb)
  • SDK testing helper for vector store adapter registrations (pm-475h)
  • SDK testing helper for package manifest resource assertions (pm-xevy)
  • SDK testing helpers for schema package registrations (pm-01bm)
  • PR #123 review: make governance hook sidecar logging fail-open (pm-mzlu)
  • Config-driven optional close reason via governance.require_close_reason (pm-peyv)

PM Tracker Evidence

Closed pm items in release window: 25
By type: Task=10, Feature=9, Chore=3, Issue=1, Story=2
By status: closed=25

Selected release-related tracker items:

  • pm-7etc [Task/closed] Agent command compatibility and package command discovery
  • pm-fhsg [Story/closed] As a maintainer tuning relevance, I want a golden-query eval harness, so that I can catch ranking regressions before release