Repository navigation
release: @didx509/credo 0.1.2 and @didx509/native 0.1.1 - #42
Merged
Merged
Conversation
Both are maintenance releases. No API changes. credo: test against credo-ts 0.7.4 (dev dependency; peer range stays ^0.7.0) and drop the stale "native not yet published" text now that @didx509/native 0.1.0 is on npm. At publish time its core dependency is rewritten to ^0.1.2. native: no code changes; the README now documents the supported key types and the upstream rejection of secp256k1. Verified: credo typecheck/lint/13 tests/build and npm pack --dry-run; native typecheck/lint/462 tests (220 vectors + parity + API + plugin)/ build and npm pack --dry-run. Signed-off-by: Ajay Jadhav <ajay@ayanworks.com>
ajile-in
force-pushed
the
release/credo-0.1.2-native-0.1.1
branch
from
November 4, 2026 17:53
355eab9 to
72eb6b6
Compare
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.
Maintenance releases for the two packages whose trusted-publisher configs have not been exercised yet. No API or behavioural changes.
@didx509/credo0.1.1→0.1.2^0.1.2@didx509/native0.1.0→0.1.1secp256k1rejection; no code changesAlso updates the published-versions table in
docs/RELEASE-FIRST.md.Why two packages at once
Both release tags are independent:
credo-v0.1.2runspublish.yml,native-v0.1.1runsprebuild.yml. They will be pushed one at a time after merge, starting with credo.Verification
typescript-credo:tsc --noEmit, ESLint, 13/13 tests, tsup build,npm pack --dry-run(didx509-credo-0.1.2.tgz, 10 files)typescript-native:tsc --noEmit, ESLint, 462/462 tests (220 upstream vectors + parity + API + plugin), tsup build,npm pack --dry-run(didx509-native-0.1.1.tgz; the publish workflow adds the prebuilds)After merge: push
credo-v0.1.2, verify, then pushnative-v0.1.1. Both use OIDC trusted publishing and will validate the remaining two publisher configs before their 2-day expiry.