Skip to content

docs: describe "Security" release notes section in release process #216

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
paullatzelsperger merged 1 commit into from
Sep 7, 2026
+10 −0
Merged

docs: describe "Security" release notes section in release process #216

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions content/en/documentation/for-contributors/guidelines/release-process.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -71,6 +71,16 @@ with the 2 workflows:
to have the artifacts available. Without this job, the next repositories will fail in compiling the project because
the upstream dependencies will be missing.

### Release notes

The GitHub release notes are auto-generated from the labels of the merged pull requests, structured into categories as
defined by the `.github/release.yaml` file that is present in every repository.

Security-relevant pull requests must be labeled with `security` during review/merge: they will then show up in the
dedicated `Security` category of the release notes, so that adopters can make an educated decision on how urgent an
upgrade is for them. Note that this does not change the backporting policy: security fixes are introduced into the main
line only, so staying up-to-date with EDC releases remains the recommended course of action.

## 2. Nightly builds
Every night we publish every artifact as a `-SNAPSHOT` with a date information, e.g. `0.14.0-20250801-SNAPSHOT`.
The workflow is also stored in the `Release` repo and it's pretty similar to the `release` ones, but the version is, as
Expand Down
Loading