chore[skiplog|notask]: backmerge release-sdk-0.12.3 — version bump, bare-fetch ^3.0.1, dev bare-subprocess ^6.1.0, changelog#2565
Closed
lauripiisang wants to merge 5 commits into
Closed
Conversation
….1; dev bare-subprocess ^6.1.0) (cherry picked from commit eff6876)
simon-iribarren
previously approved these changes
Jun 12, 2026
simon-iribarren
left a comment
Contributor
There was a problem hiding this comment.
Approved after checking CI and the focused release/backmerge diff. The package version, dependency, and changelog changes match the requested release artifacts.
Contributor
Tier-based Approval Status |
NamelsKing
previously approved these changes
Jun 12, 2026
arun-mani-j
previously approved these changes
Jun 12, 2026
…cated @qvac/response → removes bare-events 2.4.2 pin from tree)
d20d7ae
…dk-0.12.3 # Conflicts: # packages/bare-sdk/package.json # packages/sdk/CHANGELOG.md # packages/sdk/package.json
NamelsKing
approved these changes
Jun 12, 2026
Victor-Rodzko
approved these changes
Jun 12, 2026
Contributor
Author
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 this PR does
Backmerges the
@qvac/sdk@0.12.3+@qvac/bare-sdk@0.12.3(lockstep) release metadata ontomainper gitflow "Keep main aligned".[skiplog].Companion release PR
Files
packages/sdk/package.json— version0.12.2→0.12.3;bare-fetch ^2.9.1→^3.0.1(prod); devbare-subprocess ^5.2.3→^6.1.0packages/bare-sdk/package.json— version0.12.2→0.12.3;bare-fetch ^2.9.1→^3.0.1packages/sdk/changelog/0.12.3/+packages/sdk/CHANGELOG.md— changelogConflict resolution note
The release was cut off the published
0.12.2commit, whosesdk/bare-sdkdep block differs frommain(main hasbare-crypto ^1.15.0and dropped thebare-eventsline; the published base hadbare-crypto ^1.13.4+bare-events ^2.8.0). The cherry-pick conflict was resolved surgically: main's current dep lines are preserved and onlybare-fetchis changed to^3.0.1. Nobare-crypto/bare-eventsreversion.Skipped bare-* bumps
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) — same-major carets; install resolves latest within major.bare-net ^2.3.2,bare-path ^3.0.1— already at latest.bare-link >=3.0.0(peer) — range already covers 3.2.2.Migration note
bare-fetch2→3: transitive-only major; publicfetchAPI unchanged. Only 3.x change is 3.0.1 header validation — all sdk header construction is RFC-valid.bare-tlstrust-store change already ships at 2.x via the lockfile.bare-subprocess5→6 is dev-only; everyspawnSyncsite gates onstatus===0(null still takes the failure branch) and signal reads only hit log strings — no source changes required.