livebook-dev/livebook
1
1
Fork 0
mirror of https://github.com/livebook-dev/livebook.git synced 2025-09-08 05:54:20 +08:00
Code Issues Projects Releases Packages Wiki Activity

Move releasing note to RELEASE.md

Browse source
This commit is contained in:
Jonatan Kłosko 2025-01-28 20:57:55 +07:00
parent e6ee7ad964
commit 76d297a3df
2 changed files with 16 additions and 17 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

17
README.md
View file

@ -368,23 +368,6 @@ For Windows, run:
.github/scripts/app/build_windows.sh .github/scripts/app/build_windows.sh
``` ```
## Release
0. If applicable, release Kino first and update built-in notebooks to reference
the new version.
1. Make sure the latest CI "Assets" workflow finished.
2. Switch to (or create) vx.y branch.
3. If applicable cherry-pick the relevant commits from main onto the vx.y branch.
1. If you do that, push, wait for CI "Assets" workflow to finish, and pull.
3. Update version in `mix.exs` and finish changelog.
4. Run `mix hex.build` as a sanity check.
5. `git tag vx.y.z`, `git push --tags`
1. Wait for CI to finish (Docker and Desktop)
6. Run `mix hex.publish`.
7. Publish GH release with copied changelog notes.
8. If you created a branch in step 2., update main changelog to point to
the branch and bump version in mix.exs (with `-dev` suffix).
## Platinum sponsors ## Platinum sponsors
<a href="https://fly.io"> <a href="https://fly.io">

16
RELEASE.md Normal file
View file

@ -0,0 +1,16 @@
# Releasing Livebook
0. If applicable, release Kino first and update built-in notebooks to reference
the new version.
1. Make sure the latest CI "Assets" workflow finished.
2. Switch to (or create) vx.y branch.
3. If applicable cherry-pick the relevant commits from main onto the vx.y branch.
1. If you do that, push, wait for CI "Assets" workflow to finish, and pull.
3. Update version in `mix.exs` and finish changelog.
4. Run `mix hex.build` as a sanity check.
5. `git tag vx.y.z`, `git push --tags`
1. Wait for CI to finish (Docker and Desktop)
6. Run `mix hex.publish`.
7. Publish GH release with copied changelog notes.
8. If you created a branch in step 2., update main changelog to point to
the branch and bump version in mix.exs (with `-dev` suffix).