Canary releases

[IvanGoncharov]

As discussed on graphql-js-wg we decided to switch to unstable main and provide canary release every week.

Currently, there are a couple of blockers we need to address:

• Allow publishing NPM packages without updating the main (otherwise we will add a bunch of useless commits in git history).
  • Don't commit graphql/version.ts and only generate it during the build process.
  • Figure out a way to safely release versions without updating package.json
• Setup docs site for v16 we should have docs for "stable" version.
• Release v16.1.0
• Switch main to v17.0.0-alpha.0

cc: @saihaj

[dotansimha]

@IvanGoncharov are you open to introducing https://github.com/atlassian/changesets in this repo?
We are using it in many libraries, and it works well. It manages the CHANGELOG, GitHub Releases/tags, and allows to do canary releases, and also automates the stable releases process.
We recently added it in graphiql repo as well and it's really helping us there.

[n1ru4l]

Some example commit histories from graphiql:

Full commit history: https://github.com/graphql/graphiql/commits/main
Example release commit: graphql/graphiql@c1e2b5e

GraphiQL Pull request example: graphql/graphiql#2116

The bot automatically updates the message for each pushed commit to that branch:graphql/graphiql#2116 (comment)

and then people can install it by following the instructions

[yaacovCR]

It looks like this is working?

@IvanGoncharov @saihaj can we close this issue?