* Use GitHub `release` env for npm publish
As this is used for npm OIDC. Also stops passing the token given OIDC doesn't need it
* Do not write token to config
* add a script that will deploy the `netlify` dir to cloudflare pages
* switch everything from netlify over to cf pages
* fix wrangler version
* add `/` to api-docs url
* fix name of cloudflare dev project
* switch to node 18
which is now LTS
* unpin `netlify-cli`
* use `npm-ci-please` to workaound `npm ci` being broken
fixes#5115
* set version using `npm version`
which will also update the version in the package-lock
* be selective about what goes in artifact
to speed things up
* use newer `npm-ci-please`
* fix setting version on netlify
* fix permission on script
* listen on all interfaces for sauce labs
because otherwise with node 18 the server is not reachable through the proxy for some reason
* fix Netlify redirects
* remove api docs redirect
* Revert "remove api docs redirect"
This reverts commit e86af6f4f2.
* remove the index file from api docs
* also redirect index.html
* bail if new tag does not directly follow previous version
This is to try and prevent typos that could trigger an incorrect version publish into the future that cannot be undone.
refs #4841
* do not bail if tag exists, because it would for real tags
.substr() is deprecated so we replace it with .slice() which works similarily but isn't deprecated
Signed-off-by: Tobias Speicher <rootcommander@gmail.com>
Switching to alpha instead of canary because the semver sorting algorithm is alphabetic and the automated release should always have a lower precendence than manual ones.
Always prefix to the last version even when it's a prerelease so that the ordering is correct, and so that automated alpha releases are able to take precendence over manual ones when new commits are pushed.
Make the prefix `0.alpha` instead of just `alpha` so that it's easy to check if a manual version could be lower than an existing alpha version without dissalowing things like `-rc.0`
See discussion in #2822