From 8ae7ade9e6b24e9249ef382f032cd56a50b5723c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Nikola=20Forr=C3=B3?= Date: Wed, 8 Apr 2026 09:12:40 +0200 Subject: [PATCH] Add a blog post about multiple release streams support MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Nikola Forró --- posts/multiple-release-streams/index.md | 43 +++++++++++++++++++++++++ 1 file changed, 43 insertions(+) create mode 100644 posts/multiple-release-streams/index.md diff --git a/posts/multiple-release-streams/index.md b/posts/multiple-release-streams/index.md new file mode 100644 index 0000000000..c616ab82e4 --- /dev/null +++ b/posts/multiple-release-streams/index.md @@ -0,0 +1,43 @@ +--- +title: "Packit now supports multiple release streams" +date: 2026-04-08T08:00:00+00:00 +authors: nforro +tags: + - Upstream Release Monitoring + - pull-from-upstream + - downstream + - configuration +--- + +There are upstream projects that have multiple release streams and, for example, regularly release +patch versions for every active minor version. With `pull-from-upstream` you have been able to follow +only the highest stream, but that now changes. By switching `Monitoring status` of your package from +`Monitoring` to `Monitoring all`, you enable triggering `pull-from-upstream` for every released version, +not only the highest. This means you can use `version_update_mask` or `upstream_tag_include`/`upstream_tag_exclude` +(those require `upstream_project_url` to be set) to filter specific release stream you want to follow, +or have multiple `pull-from-upstream` jobs, each matching different releases and targeting different dist-git branches. + + + +## Configuration example + +For an upstream project releasing 1.7.z and 1.6.z streams, you could configure the jobs like this: + +``` +jobs: + +- job: pull_from_upstream + trigger: release + upstream_tag_exclude: ^v1\.6\.\d+$ + dist_git_branches: + - fedora-rawhide + +- job: pull_from_upstream + trigger: release + upstream_tag_include: ^v1\.6\.\d+$ + dist_git_branches: + - fedora-branched +``` + +With this configuration security backports to the 1.6 upstream branch would result in Packit opening dist-git PRs +against branched Fedoras while for any other release Packit would open dist-git PRs in Rawhide.