michaelh/zephyr
1
0
Fork 0
Code Releases Activity

ci: release: stop creating releases for RC tags

Browse source 
RC releases clutter the release page, there's no reason for keeping them
after the release is done, filter them out from the workflow so they
don't get created in the first place..

Signed-off-by: Fabio Baltieri <fabiobaltieri@google.com>
This commit is contained in:
Fabio Baltieri 2022-10-03 10:18:18 +00:00 • committed by Marti Bolivar
commit 34f74c96b0
2 changed files with 1 additions and 22 deletions
Download patch file Download diff file Expand all files Collapse all files

1
.github/workflows/release.yml vendored
View file

@ -4,6 +4,7 @@ on:
push:
tags:
- 'v*'
- '!v*rc*'
jobs:
release:

22
doc/project/release_process.rst
View file

@ -369,28 +369,6 @@ steps:
$ git tag -s -m "Zephyr 1.11.0-rc1" v1.11.0-rc1
$ git push git@github.com:zephyrproject-rtos/zephyr.git v1.11.0-rc1
#. Once the tag is pushed, a github action will create a draft release
in Github with a shortlog since the last tag. The action will also
create a SPDX manifest of the Zephyr tree and will add the file as an
asset in the release.
Go to the draft release that was created and edit as needed. If this
step fails for a reason, it can be done manually following the steps
below:
#. Create a shortlog of changes between the previous release (use
rc1..rc2 between release candidates)::
$ git shortlog v1.10.0..v1.11.0-rc1
#. Find the new tag at the top of the releases page and edit the release
with the ``Edit tag`` button with the following:
* Name it ``Zephyr 1.11.0-rc1``
* Copy the shortlog into the release notes textbox (*don't forget
to quote it properly so it shows as unformatted text in Markdown*)
* Check the "This is a pre-release" checkbox
#. Send an email to the mailing lists (``announce`` and ``devel``)
with a link to the release