Switch to @hypercerts-org/lexicon package and improve release workflow #66
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.
Summary
This PR migrates the SDK from the local
packages/lexiconworkspace to using the published@hypercerts-org/lexiconpackage (v0.10.0-beta.3) from npm. It also updates the release workflow to match the lexicon repository's approach, supporting npm Trusted Publishers and improving beta release versioning.Main Changes
1. Lexicon Package Migration
packages/lexiconlocal workspace (318 files deleted)@hypercerts-org/lexicon@0.10.0-beta.3npm packageLexiconRegistryclass - now using direct imports from lexicon package@hypercerts-org/lexicon2. Release Workflow Improvements
release-beta.ymlwith unifiedrelease.ymlsupporting both stable and beta releases.npmrcwith auth tokens)docs/PUBLISHING.mdsdk-core@x.y.z, sdk-react@x.y.z) instead of misleading workspace version3. Code Quality Improvements
.MD→.md).pnpm-store/to.gitignoreand.prettierignoreBenefits
Migration Impact
Testing
🤖 Generated with Claude Code