Chore: prepare 0.4.15 release - #220
Merged
Merged
Conversation
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.
Summary
Prepare QAMap 0.4.15 by synchronizing package and plugin versions, documenting the merged static QA and bounded execution improvements, recording the completed release gates, and updating the post-release roadmap.
Behavioral Contract
No new analyzer behavior is introduced by this release-preparation PR. The 0.4.15 package exposes the already merged account-scoped storage, divergent-copy, repository-declared E2E execution, validation-contract preservation, intent-isolation, identifier-boundary, and provider-neutral benchmark behavior under one synchronized version.
The release documentation keeps static QA, generated drafts, repository validation, provider-backed measurement, and executed product QA as separate evidence states. npm publication, Git tagging, the GitHub Release, and any OpenAI directory replacement remain post-merge actions.
Evidence
Closes #219.
Release evidence:
Checks
pnpm testpnpm bench:cipnpm bench:agent --dry-run --assertpnpm bench:contextpnpm bench:executionpnpm scanpnpm plugin:checkandpnpm plugin:smokepnpm release:checknpm publish --dry-run --access publicPublic OSS Check
Review Notes
The full release gate passed from the versioned 0.4.15 branch. QAMap static self-analysis correctly kept execution
not-runand routed the metadata-only change to repository validation, but selected the generalpnpm testcommand rather than the stronger release gate. The release verdict therefore comes from the repository-ownedpnpm release:checkevidence above, and the narrower routing gap remains follow-up work.