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` - [x] Setup docs site for v16 we should have docs for "stable" version. - [x] Release v16.1.0 - [x] Switch main to v17.0.0-alpha.0 cc: @saihaj
As discussed on graphql-js-wg we decided to switch to unstable
mainand provide canary release every week.Currently, there are a couple of blockers we need to address:
main(otherwise we will add a bunch of useless commits in git history).graphql/version.tsand only generate it during the build process.package.jsoncc: @saihaj