Add a blog post about multiple release streams support

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.
+
+<!--truncate-->
+
+## 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.