Skip to content

chore[notask]: release sdk + bare-sdk 0.12.3 — bump bare-fetch ^3.0.1#2562

Closed
lauripiisang wants to merge 3 commits into
release-sdk-0.12.3from
bump/bare-sdk-0.12.3
Closed

chore[notask]: release sdk + bare-sdk 0.12.3 — bump bare-fetch ^3.0.1#2562
lauripiisang wants to merge 3 commits into
release-sdk-0.12.3from
bump/bare-sdk-0.12.3

Conversation

@lauripiisang

Copy link
Copy Markdown
Contributor

What changed

  • @qvac/sdk and @qvac/bare-sdk prod dependency bare-fetch bumped ^2.5.1^3.0.1.
  • @qvac/sdk dev dependency bare-subprocess bumped ^5.2.3^6.1.0.
  • Both package versions bumped 0.12.20.12.3 (lockstep — the publish workflow fails if packages/sdk and packages/bare-sdk versions differ).

Skipped bare-* bumps

The following are same-major carets that already resolve to the latest version within their major at install time, so no edit is needed:

  • @qvac/sdk: bare-abort-controller, bare-crypto, bare-fs, bare-os, bare-pack, bare-process, bare-rpc, bare-runtime, bare-stream, bare-zlib, bare-readline (dev), bare-url (dev).
  • @qvac/bare-sdk: same same-major-caret list minus bare-subprocess / bare-readline / bare-url, which bare-sdk does not depend on.

Already at latest within their declared range:

  • bare-net ^2.3.2 and bare-path ^3.0.1 are already at the latest.
  • bare-link >=3.0.0 peer range already covers 3.2.2.

Migration note

  • bare-fetch 2→3 is a transitive-only major: the public fetch API is unchanged. The only 3.x behavior change is 3.0.1 header validation, and all SDK header usages (new Headers({ 'User-Agent': ... }), append('Range', 'bytes=…')) build RFC-valid headers. The bare-tls trust-store change already ships at 2.x via bun.lock.
  • bare-subprocess 5→6 is dev-only. Every spawnSync site gates on status === 0, so a null status still takes the failure branch; signal reads only feed log strings.
  • No source changes required.

🤖 Generated with Claude Code

@simon-iribarren simon-iribarren left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved after checking CI and the focused release/backmerge diff. The package version, dependency, and changelog changes match the requested release artifacts.

@github-actions

github-actions Bot commented Jun 12, 2026

Copy link
Copy Markdown
Contributor

Tier-based Approval Status

**PR Tier:** TIER1

**Current Status:** ✅ APPROVED

**Requirements:**
- 1 Team Member approval ✅ (1/1)
- 1 Team Lead OR Management approval ✅ (1/1)



---
*This comment is automatically updated when reviews change.*

NamelsKing
NamelsKing previously approved these changes Jun 12, 2026
arun-mani-j
arun-mani-j previously approved these changes Jun 12, 2026
@lauripiisang lauripiisang added the test-e2e-smoke Triggers smoke e2e test suite [Currently SDK-only] label Jun 12, 2026
…ated @qvac/response → removes bare-events 2.4.2 pin from tree)
@lauripiisang

Copy link
Copy Markdown
Contributor Author

Superseded by the 0.13.x cleanup (#2578 / backmerge #2579). The 0.12.3 line is based on published 0.12.2, whose addon ranges (transcription-whispercpp ^0.7.0, ocr-onnx ^0.5.0, transcription-parakeet ^0.6.0) pull stale transitive deps (@qvac/response → bare-events 2.4.2, bare-fetch 2.x) regardless of sdk-level bumps — a clean install proved it can't produce a clean tree. Closing in favor of 0.13.1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

test-e2e-smoke Triggers smoke e2e test suite [Currently SDK-only] tier1

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants