release(tsp-js): @openvtc/vti-tsp-js 0.2.0 - #117
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>
stormer78
added a commit
that referenced
this pull request
Aug 17, 2026
* release(tsp-js): @openvtc/vti-tsp-js 0.2.0 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> * release(core): @openvtc/pnm-core 0.4.0 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> --------- 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.
Publishes the pure-TS HPKE swap from #116 and the new
./hpkesubpath export.Minor, not patch —
sealBase/openBaseand the./hpkeexport are new public surface. The auth-modeseal/opensignatures and the wire bytes are unchanged, so existing callers need no changes.Why this must ship first
@openvtc/pnm-corenow imports@openvtc/vti-tsp-js/hpke, but the publishedvti-tsp-js@0.1.0exports map has only".":{ ".": { "types": "./dist/index.d.ts", "import": "./dist/index.js" } }So core cannot be published until this is on npm, or its import resolves to nothing (
ERR_PACKAGE_PATH_NOT_EXPORTED).Sequence
npm publish -w @openvtc/vti-tsp-jsnpm view @openvtc/vti-tsp-js@0.2.0 exportsshows./hpke"*"dependency range with^0.2.0—*has no floor, so it is satisfied by the old 0.1.0 and would let a consumer install new core against old tsp-js)npm publish -w @openvtc/pnm-coreContents
Version bump + a new
CHANGELOG.mdfor the package (it had none). No source changes — everything substantive landed in #116.Runtime dependencies are now
@noble/*only;@hpke/*is dev-only, retained so CI holds the shipped implementation byte-identical to it in both modes.Verified: lint clean, 51/51 tsp-js, 215/215 core.