Repository navigation
feat(toolkit): add public assets contract package - #4
Merged
Merged
Conversation
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.
Summary
@yunlefun/assets@0.1.0with the schema, HTTP client, Picker protocol, tests, and versioned contract documentation.Verification
pnpm buildpnpm exec vitest run(16 tests passed)pnpm typecheckpnpm lintpnpm pack --pack-destination /tmpfrompackages/assetsgit diff --checkRelease sequence
The package has not been published to npm. Drive still uses its workspace copy, so this PR does not change its runtime dependency. After review and merge, publish
@yunlefun/assets@0.1.0, verify the published tarball, then switch Drive to the published version and remove its duplicate package. Keep the standalone YunLeFun/docs site for broad developer documentation and cross-link it once the package is released.