chore[notask]: release @qvac/ai-sdk-provider 0.6.1 - #3992
Merged
opaninakuffo merged 1 commit intoAug 25, 2026
Merged
Conversation
Peer range alignment for the @qvac/cli 0.12 line. No provider API changes. - version 0.6.0 -> 0.6.1 - peerDependencies @qvac/cli ^0.10.0 || ^0.11.0 -> ^0.10.0 || ^0.11.0 || ^0.12.0 - changelog/0.6.1/ (CHANGELOG.md, CHANGELOG_LLM.md) - aggregated CHANGELOG.md rebuilt
Contributor
License compliance — cleanNo new dependency license findings in this PR. Warn-only (shadow) mode — this check does not block merges yet. Updated automatically by the canonical license compliance workflow. NOTICE presence (advisory)Missing NOTICE (advisory, does not block):
|
This was referenced Aug 21, 2026
Victor-Rodzko
approved these changes
Aug 21, 2026
opaninakuffo
approved these changes
Aug 24, 2026
opaninakuffo
marked this pull request as ready for review
August 25, 2026 10:53
Contributor
Review StatusCurrent Status: ✅ APPROVED |
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.
🎯 What problem does this PR solve?
@qvac/ai-sdk-providerdeclares its optional managed-mode peer as@qvac/cli^0.10.0 || ^0.11.0. With CLI 0.12.0 cutting (chore[notask]: release @qvac/cli 0.12.0 #3990), strict package managers would refuse to install the provider alongside it.cli→ai-sdk-provider→opencode-plugin/openclaw-plugin).📝 How does it solve it?
packages/ai-sdk-provider/package.json— version0.6.0→0.6.1packages/ai-sdk-provider/package.json—peerDependencies["@qvac/cli"]^0.10.0 || ^0.11.0→^0.10.0 || ^0.11.0 || ^0.12.0packages/ai-sdk-provider/changelog/0.6.1/—CHANGELOG.md,CHANGELOG_LLM.mdpackages/ai-sdk-provider/CHANGELOG.md— aggregate rebuilt (9 versions)Patch bump per the 0.x policy: the peer range is extended, not replaced, so
0.10.xand0.11.xconsumers are unaffected. No source changes have landed in this package since 0.6.0, and no[bc]/[api]surface moves — this is dependency-range alignment only. This mirrors the 0.2.2 release, which widened the same peer for the CLI 0.7 line.The changelog was hand-authored rather than generated. The only commit touching this package since the 0.6.0 cut is the 0.6.0 release commit itself, which reached
mainvia its backmerge (#3837) with arelease …subject that the generator's backmerge filter does not catch — running the generator would have emitted that as a spurious entry.No third-party dependency changed, so
NOTICEis unchanged and was not regenerated.Release-order note: publish only after
@qvac/cli@0.12.0is live on npm (which itself waits on@qvac/sdk@0.18.0).🧪 How was it tested?
prettier --checkclean onchangelog/0.6.1/**/*.mdandCHANGELOG.md.^0.10.0 || ^0.11.0is a strict subset of the new range, so no existing consumer resolution changes.