Automate releasing

[sync-by-unito]

Releasing Realm JavaScript is a manual process, and we should be able to more most of it to CI. Pushing a new git tag should initialize the entire release process:

• Set version (CHANGELOG.md, package.json, xcode project, dependencies.list)
• Build and upload binaries for all platforms
• Publish npm package
• Upload API documentation
• Notify in #realm-releases
• Close Jira release

[stoneyMDB]

This will be in GHA, not Jenkins. Let us know if you need more clarification. @kneth please confirm. (answering question from Slack thread)

[kneth]

Yes, it should be done in GHA. Tagging a git commit implies releasing.

[nirinchev]

I'm not sure this is the best way to do it. Such a workflow would mean that tagging a release is done before the actual release is cut rather than the other way around. It will also require us to re-do a lot of the build steps that would have been done as part of a PR anyway. My suggestion would be to use a workflow similar to the .NET release process where you have first a dispatch workflow that creates the release PR, updating the changelog and any relevant versions and then a second dispatch workflow that picks up the artifacts from the PR build and does the release - publishing to npm, uploading docs, merging the release PR, as well as finally tagging the commit and publishing a github release.

[kneth]

The PR has been merged - closing