ci: Add GH workflow to ensure pipelines new index image is an upgrade

[aThorp96]

Pipelines nightly builds use an incrementing build number to determine when to upgrade. If an index is used which has a lower build number than the currently-deployed build, the operator silently skips the upgrade.

This adds a CI job which runs any time a pipelines index is changed and warns the the PR author when a new index will not result in an upgrade.

An example of the output can be seen in this PR:

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: aThorp96
Once this PR has been reviewed and has the lgtm label, please assign elsony for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[github-actions]

🤖 Gemini AI Assistant Available

Hi @aThorp96! I'm here to help with your pull request. You can interact with me using the following commands:

Available Commands

• @gemini-cli /review - Request a comprehensive code review

  • Example: @gemini-cli /review Please focus on security and performance

• @gemini-cli <your question> - Ask me anything about the codebase

  • Example: @gemini-cli How can I improve this function?
  • Example: @gemini-cli What are the best practices for error handling here?

How to Use

1. Simply type one of the commands above in a comment on this PR
2. I'll analyze your code and provide detailed feedback
3. You can track my progress in the workflow logs

Permissions

Only OWNER, MEMBER, or COLLABORATOR users can trigger my responses. This ensures secure and appropriate usage.

---

This message was automatically added to help you get started with the Gemini AI assistant. Feel free to delete this comment if you don't need assistance.

[github-actions]

🤖 Hi @aThorp96, I've received your request, and I'm working on it now! You can track my progress in the logs for more details.

[enarha]

The description says "This adds a CI job which runs any time a pipelines index is changed ...", but wouldn't it run on any configuration change (e.g. any deploy.yaml change)? If that's the case, what will be the effect if I change a TektonConfig option for example?

[openshift-ci]

@aThorp96: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/konflux-e2e-v418-optional	ae8cecc	link	false	/test konflux-e2e-v418-optional

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.