chore[notask|skiplog]: release @qvac/cli v0.3.0#1836
Merged
NamelsKing merged 1 commit intoMay 4, 2026
Conversation
NamelsKing
approved these changes
May 1, 2026
opaninakuffo
approved these changes
May 1, 2026
Contributor
|
/review |
Contributor
Tier-based Approval Status |
NamelsKing
added a commit
that referenced
this pull request
May 4, 2026
…angelog (#1867) Brings the @qvac/cli@0.3.0 release artifacts back onto main per gitflow.md "Keep main aligned". Same shape as #1766 (the 0.2.4 backmerge precedent). - packages/cli/package.json: version 0.2.4 -> 0.3.0 - packages/cli/changelog/0.3.0/CHANGELOG.md: new - packages/cli/changelog/0.3.0/api.md: new - packages/cli/CHANGELOG.md: prepend ## [0.3.0] entry NOTE: Opened as DRAFT because the companion release PR #1836 is also still draft and 5 of its CI checks are failing. @qvac/cli@0.3.0 has not yet been published to npm (latest is 0.2.4). Mark this PR ready for review only after #1836 merges into release-cli-0.3.0 and the GPR/npm publish completes. The source-level changes (@qvac/sdk devDep ^0.10.0 + sdk.ts MIN_SDK_VERSION='0.10.0') are already on main from PR #1810 — only the release metadata needs to come back. CLI's package.json on main has no dependency drift versus release-cli-0.3.0, so unlike the SDK 0.9.2 backmerge (#1857) the package.json version bump can be safely included here. There's also no competing CLI release PR in flight on main. Co-authored-by: Dmytro Medvinskyi <functionsilence@gmail.com>
tamer-hassan-tether
pushed a commit
that referenced
this pull request
May 5, 2026
…angelog (#1867) Brings the @qvac/cli@0.3.0 release artifacts back onto main per gitflow.md "Keep main aligned". Same shape as #1766 (the 0.2.4 backmerge precedent). - packages/cli/package.json: version 0.2.4 -> 0.3.0 - packages/cli/changelog/0.3.0/CHANGELOG.md: new - packages/cli/changelog/0.3.0/api.md: new - packages/cli/CHANGELOG.md: prepend ## [0.3.0] entry NOTE: Opened as DRAFT because the companion release PR #1836 is also still draft and 5 of its CI checks are failing. @qvac/cli@0.3.0 has not yet been published to npm (latest is 0.2.4). Mark this PR ready for review only after #1836 merges into release-cli-0.3.0 and the GPR/npm publish completes. The source-level changes (@qvac/sdk devDep ^0.10.0 + sdk.ts MIN_SDK_VERSION='0.10.0') are already on main from PR #1810 — only the release metadata needs to come back. CLI's package.json on main has no dependency drift versus release-cli-0.3.0, so unlike the SDK 0.9.2 backmerge (#1857) the package.json version bump can be safely included here. There's also no competing CLI release PR in flight on main. Co-authored-by: Dmytro Medvinskyi <functionsilence@gmail.com>
Proletter
pushed a commit
that referenced
this pull request
May 24, 2026
Proletter
pushed a commit
that referenced
this pull request
May 24, 2026
…angelog (#1867) Brings the @qvac/cli@0.3.0 release artifacts back onto main per gitflow.md "Keep main aligned". Same shape as #1766 (the 0.2.4 backmerge precedent). - packages/cli/package.json: version 0.2.4 -> 0.3.0 - packages/cli/changelog/0.3.0/CHANGELOG.md: new - packages/cli/changelog/0.3.0/api.md: new - packages/cli/CHANGELOG.md: prepend ## [0.3.0] entry NOTE: Opened as DRAFT because the companion release PR #1836 is also still draft and 5 of its CI checks are failing. @qvac/cli@0.3.0 has not yet been published to npm (latest is 0.2.4). Mark this PR ready for review only after #1836 merges into release-cli-0.3.0 and the GPR/npm publish completes. The source-level changes (@qvac/sdk devDep ^0.10.0 + sdk.ts MIN_SDK_VERSION='0.10.0') are already on main from PR #1810 — only the release metadata needs to come back. CLI's package.json on main has no dependency drift versus release-cli-0.3.0, so unlike the SDK 0.9.2 backmerge (#1857) the package.json version bump can be safely included here. There's also no competing CLI release PR in flight on main. Co-authored-by: Dmytro Medvinskyi <functionsilence@gmail.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
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.
Note: be concise and prefer bullet points.
🎯 What problem does this PR solve?
@qvac/cliv0.3.0 so the new OpenAI-compatibleresponse_formatsupport inqvac serve(PR #1810, API change) reaches downstream consumers.0.2.4→0.3.0(MINOR —[api]change).📝 How does it solve it?
packages/cli/package.json: version0.2.4→0.3.0;devDependencies."@qvac/sdk"^0.9.0→^0.10.0.packages/cli/src/serve/core/sdk.ts: runtime guardMIN_SDK_VERSION0.9.0→0.10.0.packages/cli/changelog/0.3.0/(CHANGELOG.md+api.md) and prepends the[0.3.0]entry to the aggregatedpackages/cli/CHANGELOG.md.release-cli-0.3.0triggers the GPR publish; the follow-up backmerge intomainwill trigger the npm publish.🧪 How was it tested?
bun lint,bun run build, andbun testfrompackages/cli/are clean.generate-changelog-sdk-pod.cjs); the0.3.0folder and aggregated entry match the format used by previous CLI releases (e.g. chore[notask|skiplog]: release @qvac/cli v0.2.4 #1752).response_formatflow itself was already exercised end-to-end in the source PR (#1810).🔌 API Changes
response_formatis now wired throughqvac serve's OpenAI-compatiblePOST /v1/chat/completions. The body field is parsed, validated, and forwarded to the SDK asresponseFormat, enabling structured-output requests (text/json_object/json_schema).Full per-version changelog:
packages/cli/changelog/0.3.0/CHANGELOG.md· API details:api.mdRelated PRs
response_formatsupport