Repository navigation
fix: run the latest Vega web remote instead of a pinned commit (v3.1.1) - #13
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.
pnpm remote:veganow runsnpx github:boothwall/vega-web-remotewithout a commit pin, so it always picks up the remote's latest release. The README, the development guide and the event guide drop the pinned-release wording and link the remote's repo instead of the v0.2.2 tree. The changelog releases this as 3.1.1.Validation: Prettier is clean, and
pnpm remote:vega --helpfetches the remote and prints its usage. Nothing else changes.