[DRAFT] chore: set up auto for versioning/release management #497
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.
Motivation
Request from @domoritz as part of the Vega org-wide automation effort. Note this is the first time we're applying auto to a Monorepo (with multiple yarn workspaces) in 1 repo in the Vega org, but it's possible (see this repo for reference).
See vega/vega-lite#7984 for a similar PR.
Changes
Pre-merge checklist for a repo admin
next
from the current head ofmaster
https://github.com/vega/react-vega/tree/nextnext
the base branch of this PR instead ofmaster
next
the base branch for the whole repostable
from the latest tagv7.5.1
https://github.com/vega/react-vega/tree/stableskip-release
andreleased
in this repo (the first is used to tell auto not to release anything if this PR is released, the second is used to tag PRs that have been released).📦 Published PR as canary version:
7.5.2--canary.497.1504252.0
✨ Test out this PR locally via:
npm install react-vega@7.5.2--canary.497.1504252.0 # or yarn add react-vega@7.5.2--canary.497.1504252.0