Rename package to Diamond - #26
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
sparql-d1to Diamond /@gnolith/diamondMigration impact
Existing users should replace
sparql-d1imports with@gnolith/diamond. The old npm package will be retained and deprecated with a migration notice after the scoped package publishes successfully. The prior GitHub URL redirects tognolith/diamondthrough GitHub's repository transfer.Validation
npm run check(113 tests, coverage, build, examples, Worker, scoped consumer install, licenses, readiness)npm run conformance(490/490)npm run benchmark:checknpm run benchmark:storage:checknpm run release:check -- v0.3.0git diff --check