Merge pull request #115 from Amoghrd/dep-graph-12-1

Update dep graph for 1.12.1

Author: jotak

Konflux.md

@@ -162,7 +162,11 @@ After a release, the following steps should be done:
 3. [**y-stream release**] update the konflux components for these branches (see section "Redirecting branches" below - you must be connected to the konflux CI cluster)
 4. [**any release**] wait for the nudging PRs generated after those changes to appear and be merged automatically
 5. [**any release**] update ystream and zstream in [netobserv-catalog](https://github.com/netobserv/netobserv-catalog):
-  - updating the dependency graph (replace tags...) with the version just-released
+  - update the dependency graph for the next version. For example, after releasing 1.12.1 and bumping repos to 1.12.2:
+    - in `templates/z-stream.yaml`: add `v1.12.2 replaces v1.12.1` to the stable channel entries, pin the 1.12.1 bundle image to its released SHA (from `released.yaml`), and add a new `# 1.12.2` bundle entry pointing to `...bundle-zstream:latest`
+    - update `templates/z-stream.Dockerfile-args` to `BUILDVERSION=1.12.2`
+    - in `templates/y-stream.yaml`: update the `replaces` for the current y-stream entry to point to the just-released version (e.g. `v2.0.0 replaces v1.12.1` instead of `v1.12.0`), and add the released version's channel entry and bundle image with its SHA
+    - for y-stream releases, also apply the same z-stream pattern to `y-stream.yaml` and `y-stream.Dockerfile-args`
   - only after step 4. is complete AND the bundle on-push jobs succeeded, regenerate all catalogs
 6. [**any release**] update the `ReleasePlanAdmission` objects in gitlab for next versions. See [merge request example](https://gitlab.cee.redhat.com/releng/konflux-release-data/-/merge_requests/20432)