🤖 [RHTAS-build-bot] [main] Update FBC images - rhtas-operator

[JasonPowr]

🤖 This is an automated PR that updates the FBCs to their latest versions.

Summary by Sourcery

New Features:

• Add rhtas-operator v1.3.2 bundle to the FBC catalogs for OpenShift 4.16 through 4.20.

[sourcery-ai]

Reviewer's Guide

This PR updates the rhtas-operator FBC graphs and catalogs for OCP versions 4.16–4.20 to add the new bundle version v1.3.2, wiring it into all relevant channels with correct replaces/skips metadata and image digest.

Flow diagram for rhtas_operator v1_3_x upgrade graph after adding v1_3_2

flowchart LR
  subgraph stable_v1_3_channel
    b130_s[bundle rhtas-operator v1.3.0]
    b131_s[bundle rhtas-operator v1.3.1]
    b132_s[bundle rhtas-operator v1.3.2]

    b130_s -->|replaced_by| b131_s
    b130_s -->|replaced_by| b132_s

    b132_s -.skips.-> b130_s
    b132_s -.skips.-> b131_s
  end

  subgraph stable_channel
    b120[bundle rhtas-operator v1.2.0]
    b121[bundle rhtas-operator v1.2.1]
    b130[bundle rhtas-operator v1.3.0]
    b131[bundle rhtas-operator v1.3.1]
    b132[bundle rhtas-operator v1.3.2]

    b130 -->|replaced_by| b131
    b130 -->|replaced_by| b132

    b131 -.skips.-> b120
    b131 -.skips.-> b121
    b131 -.skips.-> b130

    b132 -.skips.-> b120
    b132 -.skips.-> b121
    b132 -.skips.-> b130
    b132 -.skips.-> b131
  end

Loading

File-Level Changes

Change	Details	Files
Add rhtas-operator v1.3.2 bundle to all supported OCP versions and channels with appropriate upgrade graph metadata.	Extend stable-v1.3 and stable channels in each versioned graph.yaml (v4.16–v4.20) with a new entry for rhtas-operator.v1.3.2 that replaces v1.3.0 and skips both v1.3.0 and v1.3.1 (and older 1.2.x where applicable). Append a new olm.bundle entry in each graph.yaml referencing the v1.3.2 bundle image digest registry.redhat.io/rhtas/rhtas-operator-bundle@sha256:c4bc34c67cfa2e20441998713ed7c7fa7ed5424e40e54781dbb692699d68c6bf. Regenerate or update catalog.json files for rhtas-operator under v4.16–v4.20 catalogs to reflect the inclusion of the v1.3.2 bundle in the FBC.	v4.16/rhtas-operator/graph.yaml v4.17/rhtas-operator/graph.yaml v4.18/rhtas-operator/graph.yaml v4.19/rhtas-operator/graph.yaml v4.20/rhtas-operator/graph.yaml v4.16/rhtas-operator/catalog/rhtas-operator/catalog.json v4.17/rhtas-operator/catalog/rhtas-operator/catalog.json v4.18/rhtas-operator/catalog/rhtas-operator/catalog.json v4.19/rhtas-operator/catalog/rhtas-operator/catalog.json v4.20/rhtas-operator/catalog/rhtas-operator/catalog.json

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey there - I've reviewed your changes - here's some feedback:

• In the new 1.3.2 channel entries, consider whether replaces should point to v1.3.1 instead of v1.3.0 (with 1.3.0 in skips) to keep the upgrade graph linear and more closely aligned with how previous patches were chained.
• Double-check that the updated catalog.json files reference the same 1.3.2 bundle image digest and channel metadata as the corresponding graph.yaml entries to avoid mismatches between the FBC graph and catalog content.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- In the new 1.3.2 channel entries, consider whether `replaces` should point to v1.3.1 instead of v1.3.0 (with 1.3.0 in `skips`) to keep the upgrade graph linear and more closely aligned with how previous patches were chained.
- Double-check that the updated catalog.json files reference the same 1.3.2 bundle image digest and channel metadata as the corresponding graph.yaml entries to avoid mismatches between the FBC graph and catalog content.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}