release(core): @openvtc/pnm-core 0.4.0 - #118
Merged
Merged
Conversation
Publishes the pure-TS HPKE swap (#116) and the new `./hpke` subpath export. Minor rather than patch: `sealBase`/`openBase` and the `./hpke` export are new public surface. The auth-mode `seal`/`open` signatures and the wire bytes are unchanged, so existing callers need no changes. `@openvtc/pnm-core` cannot be published until this is on npm — it imports `@openvtc/vti-tsp-js/hpke`, and the published 0.1.0 exports map has only ".". Signed-off-by: Glenn Gore <glenn.g@affinidi.com>
Ships the HPKE consolidation (#116) and the trust-task-error 0.x fix (#115). Minor rather than patch: `@hpke/*` leaves the runtime dependency set and the `@openvtc/vti-tsp-js` range gains a floor. The range moves from `*` to `^0.2.0`. `*` expressed no minimum, so it was satisfied by the published 0.1.0 — which has no `./hpke` export — and a consumer whose lockfile pinned 0.1.0 would have installed this release against it and failed to resolve the import. **Do not publish this until `@openvtc/vti-tsp-js@0.2.0` is on npm** (#117). Signed-off-by: Glenn Gore <glenn.g@affinidi.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
1 participant
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.
Ships the HPKE consolidation (#116) and the
trust-task-error0.xfix (#115), both currently unreleased.Important
Blocked on #117. Do not merge or publish until
@openvtc/vti-tsp-js@0.2.0is on npm. This PR is branched off #117, so its diff shows both commits until that one merges — it will resolve to just the core commit afterwards.Minor, not patch —
@hpke/*leaves the runtime dependency set, and the@openvtc/vti-tsp-jsrange gains a floor.The
*range is the important partThe dependency moves from
"*"to"^0.2.0".*expresses no minimum, so it is satisfied by the publishedvti-tsp-js@0.1.0— which has no./hpkeexport. A consumer whose lockfile already pins0.1.0would install this release against it, andimport { openBase } from "@openvtc/vti-tsp-js/hpke"would fail to resolve. Publishing in the right order narrows that window; the floor is what closes it.*works fine inside the workspace and is wrong for published consumers, so this is worth fixing on its own merits.Publish sequence
npm publish -w @openvtc/vti-tsp-jsnpm view @openvtc/vti-tsp-js@0.2.0 exportsshows./hpkenpm publish -w @openvtc/pnm-coreContents
Version bumps (
core0.4.0; the^0.4.0reference inextensionandpwa), the dependency floor, and the CHANGELOG. No source changes.The changelog records two things worth flagging for reviewers:
hpkeOpenhad no direct test coverage before feat(tsp-js): pure-TS HPKE on @noble — one implementation for browser, Node, and React Native #116 — core's 208 tests never exercised the sealed-bundle decryption path. It now has seven cases where the sealing side is deliberately hpke-js rather than our own code.pnm-coreis notcrypto.subtle-free. WebAuthn, the PRF vault wrap, DID verification methods and trust-task canonicalisation all still use it. This removes HPKE from that list, not the rest — worth not overstating the React Native story downstream.Verified: lint clean, build clean, 51/51 tsp-js, 215/215 core, MV3 bundle still a single chunk with no dynamic
import()and no hpke-js.^0.2.0resolves to the workspace copy, so CI passes before tsp-js is published.