docs: record 0.14.1 in the changelog and point the README at it - #508
Merged
Conversation
The 0.14.1 tag shipped without a changelog entry, so the README still advertised v0.14.0 while PyPI served 0.14.1, and release.yml fell back to a git-log release body because no `## [0.14.1]` section existed for it to extract. - CHANGELOG: new [0.14.1] section covering the two HIGH authorisation bypasses closed in the MCP output port and the SDK 1.x/2.x dual-support work, both from #492, plus the legal-entity correction that was sitting under [Unreleased]. - CHANGELOG: [Unreleased] now carries the release-image grype-ignore work. - CHANGELOG: added the [0.14.1] compare link. - README: latest-version line 0.14.0 -> 0.14.1. Verified: PyPI serves 0.14.1; SchemaManager.latest_bundled_version() returns 0.7.5, which is what the README already states (0.7.6 is preview-gated); and the release.yml awk extraction returns the new section rather than falling back.
📄 Documentation ReminderThis PR appears to be missing a documentation reference. Our docs live in a separate repo. Please update the PR description with one of:
See the Contributing Guide for details. |
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
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.
The
v0.14.1tag shipped without a changelog entry. Three consequences:README.mdstill advertised v0.14.0 while PyPI serves 0.14.1.release.ymlgenerates its release body by extracting the## [X.Y.Z] — datesection from
CHANGELOG.md; with no[0.14.1]section it fell back to a gitlog, so the v0.14.1 GitHub release notes are raw commit subjects.
in the changelog, which matters for anyone auditing the security history.
Changes
CHANGELOG.md— new[0.14.1] — 2026-08-03section:self-attested caller attributes were flattened into one dict, so a caller
could self-attest an uncovered
rowFilter— including another tenant's — orslip
model/useCasepast theagentPolicygate whenever a customFLUID_MCP_JWT_CLAIM_MAPPINGomitted them).fluid_build/_mcp_compat.py,including the twelve camelCase reads that were failing silently under 2.x.
[Unreleased].CHANGELOG.md—[Unreleased]now holds the release-image grype-ignorework, and the
[0.14.1]compare link is added.README.md— latest-version linev0.14.0→v0.14.1.Verification
0.14.1(queried the JSON index directly, not local pip).SchemaManager.latest_bundled_version()returns0.7.5, which is what theREADME already states —
0.7.6is preview-gated viaPREVIEW_VERSIONS, sothe README needed no schema change.
release.yml's awk extraction against the edited file: it returns the new[0.14.1]body instead of falling back to git log.0.8.2and0.8.3rc1which were already missing before this change and are left alone.Documentation only — no code, no tests affected.