Skip to content

chore[notask]: release @qvac/ai-sdk-provider 0.6.1 - #3992

Merged
opaninakuffo merged 1 commit into
release-ai-sdk-provider-0.6.1from
chore/ai-sdk-provider-0.6.1-changelog
Aug 25, 2026
Merged

chore[notask]: release @qvac/ai-sdk-provider 0.6.1#3992
opaninakuffo merged 1 commit into
release-ai-sdk-provider-0.6.1from
chore/ai-sdk-provider-0.6.1-changelog

Conversation

@simon-iribarren

Copy link
Copy Markdown
Contributor

🎯 What problem does this PR solve?

  • @qvac/ai-sdk-provider declares 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.
  • Second package in the agent-stack cascade (cliai-sdk-provideropencode-plugin / openclaw-plugin).

📝 How does it solve it?

  • packages/ai-sdk-provider/package.json — version 0.6.00.6.1
  • packages/ai-sdk-provider/package.jsonpeerDependencies["@qvac/cli"] ^0.10.0 || ^0.11.0^0.10.0 || ^0.11.0 || ^0.12.0
  • packages/ai-sdk-provider/changelog/0.6.1/CHANGELOG.md, CHANGELOG_LLM.md
  • packages/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.x and 0.11.x consumers 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 main via its backmerge (#3837) with a release … 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 NOTICE is unchanged and was not regenerated.

Release-order note: publish only after @qvac/cli@0.12.0 is live on npm (which itself waits on @qvac/sdk@0.18.0).

🧪 How was it tested?

  • Release metadata only — no source changes, so no behavioural test surface.
  • prettier --check clean on changelog/0.6.1/**/*.md and CHANGELOG.md.
  • Peer range verified as additive: ^0.10.0 || ^0.11.0 is a strict subset of the new range, so no existing consumer resolution changes.

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
@github-actions

Copy link
Copy Markdown
Contributor

License compliance — clean

No 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):

  • ./.github/actions/release-merge-guard
  • ./docs/website
  • ./packages/ggml-coload-smoke
  • ./packages/fabric/test/integration
  • ./packages/inference-addon-cpp/mobile
  • ./packages/sdk/e2e
  • ./packages/llm-llamacpp/benchmarks/performance
  • ./packages/llm-llamacpp/benchmarks/server
  • ./packages/vla-ggml/sim/server
  • ./packages/embed-llamacpp/benchmarks/performance
  • ./packages/embed-llamacpp/benchmarks/server
  • ./packages/asr-ggml/benchmarks/server

@opaninakuffo
opaninakuffo marked this pull request as ready for review August 25, 2026 10:53
@opaninakuffo
opaninakuffo requested review from a team as code owners August 25, 2026 10:53
@github-actions

Copy link
Copy Markdown
Contributor

Review Status

Current Status: ✅ APPROVED
Approvals so far: Team Lead: 1, Member: 1

@opaninakuffo
opaninakuffo merged commit 42bd888 into release-ai-sdk-provider-0.6.1 Aug 25, 2026
18 checks passed
@opaninakuffo
opaninakuffo deleted the chore/ai-sdk-provider-0.6.1-changelog branch August 25, 2026 10:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants