[DRAFT] chore: set up auto for versioning/release management

[hydrosquall]

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 https://github.com/vega/vega-lite/pull/7984 for a similar PR.

Changes

• [x] Adapt the setup in https://github.com/vega/vega-lite/pull/7984
• [ ] Update documentation in contributing
• [x] Figure out how to run a test change in a monorepo (one of my commits adds a console log- it can be removed once we confirm that moving forward on this PR is recommended by @kristw ).

Pre-merge checklist for a repo admin

• [x] Create a branch called next from the current head of master https://github.com/vega/react-vega/tree/next
  • [x] make next the base branch of this PR instead of master
  • [ ] make next the base branch for the whole repo
• [x] Create a branch called stable from the latest tag v7.5.1 https://github.com/vega/react-vega/tree/stable
• [x] Make a tagged release of the latest tag (This is done: https://github.com/vega/vega-lite/releases/tag/v7.5.1 )
• [x] Create tags called skip-release and released 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

:sparkles: Test out this PR locally via:

npm install [email protected]
# or 
yarn add [email protected]

[domoritz]

@kristw is maintaining this repo so I will let him decide how we wants to handle things.

[kristw]

Appreciate the effort in adding automation. Let me take some time to read through.

[hydrosquall]

Given the complications that arose with Auto in the future ( see https://github.com/vega/vega-lite/issues/8370 ), I think it is best if we close this PR for now. If we revisit automatic releases in the future, we may be better off using release-it, which is more actively maintained and does not have this version drift bug (no action needed, just FYI @domoritz ).