Skip to content

Commit eff6876

Browse files
committed
chore[notask]: release sdk + bare-sdk 0.12.3 (bump bare-fetch to ^3.0.1; dev bare-subprocess ^6.1.0)
1 parent be3cef2 commit eff6876

5 files changed

Lines changed: 35 additions & 5 deletions

File tree

packages/bare-sdk/package.json

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
{
22
"name": "@qvac/bare-sdk",
3-
"version": "0.12.2",
3+
"version": "0.12.3",
44
"license": "Apache-2.0",
55
"description": "Bare-targeted slim assembly of the QVAC SDK. Consumers install only the addon packages they need and register plugins explicitly. No addon dependencies pulled in by default.",
66
"repository": {
@@ -164,7 +164,7 @@
164164
"bare-abort-controller": "^1.0.0",
165165
"bare-crypto": "^1.13.4",
166166
"bare-events": "^2.8.0",
167-
"bare-fetch": "^2.5.1",
167+
"bare-fetch": "^3.0.1",
168168
"bare-fs": "^4.5.1",
169169
"bare-net": "^2.2.0",
170170
"bare-os": "^3.6.2",

packages/sdk/CHANGELOG.md

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,17 @@
11
# Changelog
22

3+
## [0.12.3]
4+
5+
📦 **NPM:** https://www.npmjs.com/package/@qvac/sdk/v/0.12.3
6+
7+
This is a dependency-maintenance patch. `@qvac/sdk` and `@qvac/bare-sdk` adopt `bare-fetch` 3.x and the SDK moves its dev-only `bare-subprocess` to 6.x. There are no source or public API changes.
8+
9+
## Maintenance
10+
11+
Bump bare-fetch to ^3.0.1 (adopt 3.x; public fetch API unchanged). Bump dev bare-subprocess to ^6.1.0.
12+
13+
The bare-fetch 2→3 jump is a transitive-only major: the public fetch API is unchanged. The only 3.x behavior change is 3.0.1 header validation, and every SDK header construction (`new Headers({ 'User-Agent': ... })`, `append('Range', 'bytes=…')`) already builds RFC-valid headers. The bare-subprocess 5→6 bump is dev-only and affects no shipped code.
14+
315
## [0.12.2]
416

517
📦 **NPM:** https://www.npmjs.com/package/@qvac/sdk/v/0.12.2
Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
# Changelog v0.12.3
2+
3+
Release Date: 2026-06-12
4+
5+
## 🔧 Maintenance
6+
7+
- Bump bare-fetch to ^3.0.1 (adopt 3.x; public fetch API unchanged). Bump dev bare-subprocess to ^6.1.0.
Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
# QVAC SDK v0.12.3 Release Notes
2+
3+
📦 **NPM:** https://www.npmjs.com/package/@qvac/sdk/v/0.12.3
4+
5+
This is a dependency-maintenance patch. `@qvac/sdk` and `@qvac/bare-sdk` adopt `bare-fetch` 3.x and the SDK moves its dev-only `bare-subprocess` to 6.x. There are no source or public API changes.
6+
7+
## Maintenance
8+
9+
Bump bare-fetch to ^3.0.1 (adopt 3.x; public fetch API unchanged). Bump dev bare-subprocess to ^6.1.0.
10+
11+
The bare-fetch 2→3 jump is a transitive-only major: the public fetch API is unchanged. The only 3.x behavior change is 3.0.1 header validation, and every SDK header construction (`new Headers({ 'User-Agent': ... })`, `append('Range', 'bytes=…')`) already builds RFC-valid headers. The bare-subprocess 5→6 bump is dev-only and affects no shipped code.

packages/sdk/package.json

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
{
22
"name": "@qvac/sdk",
3-
"version": "0.12.2",
3+
"version": "0.12.3",
44
"license": "Apache-2.0",
55
"repository": {
66
"type": "git",
@@ -212,7 +212,7 @@
212212
"bare-abort-controller": "^1.0.0",
213213
"bare-crypto": "^1.13.4",
214214
"bare-events": "^2.8.0",
215-
"bare-fetch": "^2.5.1",
215+
"bare-fetch": "^3.0.1",
216216
"bare-fs": "^4.5.1",
217217
"bare-net": "^2.2.0",
218218
"bare-os": "^3.6.2",
@@ -242,7 +242,7 @@
242242
"@types/semver": "^7.7.1",
243243
"@types/tar-stream": "^3.1.4",
244244
"bare-readline": "^1.2.0",
245-
"bare-subprocess": "^5.2.3",
245+
"bare-subprocess": "^6.1.0",
246246
"bare-url": "^2.4.3",
247247
"brittle": "^3.19.1",
248248
"chromadb": "^3.0.14",

0 commit comments

Comments
 (0)