docs(changelog): post-v0.5.0 cleanup of orphaned phase refs#52
Merged
Conversation
Doc-expert review of the v0.5.0 release prep PR (#51) flagged two items that survived the CHANGELOG consolidation: 1. ``CHANGELOG.md:2075`` carried ``"None for sensor users on v0.4.0 Phase 1."`` inside the demoted Agent identity model foundation sub-section. The "v0.4.0 Phase 1" label was the original draft heading that consolidation collapsed away, leaving the phrase pointing at nothing. Replaced with ``"None."`` -- the surrounding ``### Breaking changes`` heading already scopes it. 2. ``CHANGELOG.md:782/883/1260`` carried ``"v0.6 enforces policy decisions as configured"`` prose written when MCP Policy was still in soft-launch and v0.6 was the target enforcement release. D145 retired the soft-launch override before v0.5.0 shipped, so enforcement is the current behavior, not a planned v0.6 change. Rewrote to describe the present-tense behavior (``Block decisions raise MCPPolicyBlocked; warn decisions log and pass through``). 3. ``CHANGELOG.md:9`` minor typo (``v0.5.0 phase`` lowercase) -> ``v0.5.0 Phase 4`` capitalized to match the rest of the doc. No code changes. Release tag v0.5.0 (commit 1ba1fcd) is unchanged and published artifacts on PyPI / Docker Hub / GitHub Releases are not affected. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
4 tasks
pykul
added a commit
that referenced
this pull request
May 27, 2026
Post-release cleanup addressing the DIRTY findings from the v0.5.1 prep PR (#54) reviewer fan-out. Mirrors yesterday's #52 pattern. CHANGELOG.md: - Promotes the bundled-Postgres password breaking change out of "Security / hardening" into its own "### Breaking changes" subsection (the intro paragraph cross-references "see the breaking note below" so the subsection had to exist) - Drops inline "(D100)" reference per CLAUDE.md rule 41 (no D-numbers in code/comments/CHANGELOG prose; describe behavior in plain English instead). Replaced with "zero-config default-token path" - Tightens intro: "one bugfix, one breaking change, five hardening / infrastructure items" (was "six hardening items deferred", which conflated the bugfix and CI-gate items with security work) - Updates [flightdeck] WARN reference to include the colon (matches the actual emitted format after the consistency fix below) plugin/README.md: - Documents FLIGHTDECK_QUIET in the env-var table (the v0.5.1 WARN message instructs users to set it; the table previously had no row, leaving operators stranded) plugin/hooks/scripts/observe_cli.mjs: - WARN format consistency: "[flightdeck] WARN: ..." (colon) to match the existing "[flightdeck] WARN:" pattern at lines 223 and 295. Behavior unchanged, format aligns plugin/tests/observe_cli.test.mjs: - 3 new unit tests pinning the tok_dev WARN contract: emits when FLIGHTDECK_TOKEN unset, suppressed by FLIGHTDECK_QUIET=1, silent when FLIGHTDECK_TOKEN is explicitly set. Each test captures process.stderr.write into a buffer and restores in finally so a resolveConfig failure doesn't leave the runner with a broken stderr stream. 91 → 94 tests. .github/workflows/ci.yml: - Pins azure/setup-helm to commit SHA bf6a7d304b... (was @v4 mutable tag). Matches the SHA-pinning discipline established across all 7 actions in release.yml; closes the gap surfaced by the security reviewer. Deferred to Supervisor scope decision (NOT in this PR): - api.auth.jwtSecret / api.auth.adminPassword `required` guard in helm/templates/secret.yaml. Same shape as the postgres.password fix but a SECOND breaking change for existing helm installs that bootstrap auth via post-render or a separate secret. Needs scope authorization before landing; recommend v0.5.2. Co-authored-by: pykul <omria@Omri-PC.localdomain> Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Doc-expert review of PR #51 surfaced three CHANGELOG entries that survived the v0.5.0 release consolidation but no longer make sense to a reader:
"None for sensor users on v0.4.0 Phase 1."(the "v0.4.0 Phase 1" label was the draft heading that consolidation collapsed away)"v0.6 enforces policy decisions"prose from when MCP Policy was in soft-launch and v0.6 was the target enforcement release. D145 retired the soft-launch before v0.5.0 shipped, so enforcement is the current behaviour, not a v0.6 promise.v0.5.0 phase→v0.5.0 Phase 4)10 insertions, 11 deletions. No code changes; the published v0.5.0 artefacts (PyPI / Docker Hub / GitHub Release) are unaffected.
Deferred to v0.5.1 (from same review batch)
Not included here, queued as follow-up work:
release.yml),helmchart default Postgres password fallback ("flightdeck"),tok_devsilent default in the plugin'sobserve_cli.mjs(now amplified by marketplace install path)"0.1.0"inapi/docs/andingestion/docs/; absenthelm lint+ marketplace.json schema gates in CI;dashboard/package.jsonversion still at0.1.0(private, not published)Test plan
🤖 Generated with Claude Code