Repository navigation
Version Packages: Orbit 0.20.0 - #18
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.
Release all five public Orbit packages at 0.20.0: core, data, engine-cosmos, omnigraph, and react.
This is the version commit generated by the repository's Changesets workflow after #17. It consumes the approved changeset and updates package versions and changelogs for guided CSV imports, bounded and cancellable preparation, optional columnar output, live minimap positions, shared label-position caching, and the verified first-graph quickstart.
The feature PR passed all five CI jobs before merge. This PR must pass the same checks before merge; merging triggers the existing build-and-pack-smoke-gated npm publishing workflow. Public npm versions and tarball integrity will be verified after publication.
The workflow could push this generated branch but repository policy prevented its bot token from opening a PR, so this PR was opened using the authenticated maintainer account.