Release process: nightly packages

[pomek]

📝 Provide a description of the improvement

The goal is to publish CKEditor 5 packages from the #master branch as the @nightly version.

Scope

• The publishing step should be executed only if CRON triggered Travis.
• Use Uber CI.
  • The publishing phase should be the first task executed on Uber CI.
• Authenticate npm on Travis CI.
  • We can use ~/.npmrc file with auth token.
  • We do not need to call npm login.
  • It works. We just released mrgit.
• Generate the version number for nightly releases:
  • 0.0.0-nightly-YYYYMMDD.0
  • If .0 is taken, take the next one.
• Flow
  • Prepare CKEditor 5 packages.
  • Publish CKEditor 5 packages.
  • Prepare Internal packages.
  • Publish Internal packages.
  • Update the CS-Client based on the release commit.
    • All version references should point to the nightly number.
  • Prepare CF packages.
  • Publish CF packages.
  • If something goes wrong, let us know (Slack). Otherwise, keep it silent.
• Use the published packages to execute tests, build docs, etc.
• Update the flowchart of what Uber CI does.

---

If you'd like to see this improvement implemented, add a 👍 reaction to this post.