Feature: Improved release process

[etrepum]

Follow-up to #6169 #6204

Once we have nightly releases it would be nice to make the following enhancements:

Nightly releases

• Only run nightly releases if main has changed since the last one

Latest channel releases

• Create the PR from the versioned release branch (possibly automated) (example: https://github.com/facebook/lexical/pull/6084)
• Create the draft release from the versioned release tag (probably automated) (example: https://github.com/facebook/lexical/releases/tag/v0.15.0)
• Perform the npm publish from the release tag after the release is published (this fixes the race condition on main)
• Update documentation accordingly

Proposed new workflow

1. Run "Create Release Branch" action with patch or minor increment
   • Automatically creates or updates the PR and initial release branch (if we can get permissions to do it, see comment)
   • Automatically creates or updates the tag & channel branch
   • Automatically creates or updates the draft release
2. PR should be reviewed.
   • If any changes need to be made, do them in separate PRs, merge to main, and start over at step 1
3. Merge PR
   • This updates main, so the CHANGELOG, package.json, error-codes, etc. are all in sync
4. Edit draft release (fix formatting, add highlights, etc.) and publish
   • Automatically publishes the contents of the release tag to npm
   • Note: The latest release is used as an input for 1. when generating the CHANGELOG

Open questions

• Do we want to support release channels other than nightly and latest?
• Is there a use case for prerelease version increment and the next channel? If so, we should implement it, if not then we should remove support for it.

---

I have a prototype of the new workflows in a separate repo that I have deliberately built with similar organization around the workflows and release processes with all of this working: https://github.com/etrepum/lexical-builder/tree/main/.github/workflows

[etrepum]

Regarding PRs, it seems that it might be worth leaving that as a manual process unless the facebook organization and lexical repo allows actions to create PRs. It's not on by default.