chore[notask|skiplog]: release @qvac/registry-schema v0.2.0#2034
Merged
yuranich merged 1 commit intoMay 14, 2026
Conversation
Move hyperdb from dependencies to peerDependencies (tetherto#1905). Minor bump so 0.x ^-ranges don't auto-promote — install contract changed for standalone yarn-1 / legacy-peer-deps consumers. Co-authored-by: Cursor <cursoragent@cursor.com>
opaninakuffo
approved these changes
May 13, 2026
NamelsKing
approved these changes
May 14, 2026
Contributor
Author
|
/review |
Contributor
Tier-based Approval Status |
yuranich
merged commit d5f5723
into
tetherto:release-qvac-registry-schema-0.2.0
22 of 24 checks passed
yuranich
added a commit
that referenced
this pull request
May 15, 2026
Proletter
pushed a commit
that referenced
this pull request
May 24, 2026
Move hyperdb from dependencies to peerDependencies (#1905). Minor bump so 0.x ^-ranges don't auto-promote — install contract changed for standalone yarn-1 / legacy-peer-deps consumers.
Proletter
pushed a commit
that referenced
this pull request
May 24, 2026
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
3 participants
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 problem does this PR solve?
Publish
@qvac/registry-schema v0.2.0so thepeerDependencies-only Holepunch-lib classification from #1905 actually reaches npm. The repo's0.1.2manifest was edited in place by #1905 but never re-published — the npm artifact still shipshyperdbas a harddependency, so SDK consumers still get duplicated singletons.How does it solve it?
@qvac/registry-schemafrom0.1.2to0.2.0. Minor (not patch) so existing^0.1.xranges in downstream consumers don't auto-promote — the install contract changed for standalone yarn-1 /legacy-peer-deps=trueconsumers and they need an explicit opt-in.[0.2.0]changelog entry pointing at chore[notask]: move Holepunch libs to peerDependencies #1905.On merge to
release-qvac-registry-schema-0.2.0,publish-registry-server.ymlpublishes to npm.How was it tested?
Metadata-only release; no code changes. Verification of the dedup behaviour is done downstream once the SDK consumes the bumped peers (see follow-ups).
Follow-ups
package.json+CHANGELOG.mdbumps intomain(per gitflow step 4).@qvac/registry-client v0.5.0— separate release PR, currently draft, blocked on this one being published to npm.@qvac/registry-client: ^0.5.0and@qvac/rag: ^0.5.0to actually deliver dedup to apps.