NO-ISSUE: chore: bump quay master version

[jbpratt]

Signed-off-by: Brady Pratt bpratt@redhat.com

Summary by CodeRabbit

• Updated Quay CI configuration to target quay-v5.0.0 for the master branch.
• Added the redhat-5.0 branch configuration with quay-v5.0.0 and quay-v5.0.z targets.
• Enabled default validation for the new branch configuration.

[openshift-ci-robot]

@jbpratt: This pull request explicitly references no jira issue.

Details

In response to this:

Signed-off-by: Brady Pratt bpratt@redhat.com

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-merge-bot]

[REHEARSALNOTIFIER]
@jbpratt: no rehearsable tests are affected by this change

Note: If this PR includes changes to step registry files (ci-operator/step-registry/) and you expected jobs to be found, try rebasing your PR onto the base branch. This helps pj-rehearse accurately detect changes when the base branch has moved forward.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Pro Plus

Run ID: bbef5194-fc9a-4209-8162-ca6993e312fe

📥 Commits

Reviewing files that changed from the base of the PR and between ec91098 and ec46c49.

📒 Files selected for processing (1)

• core-services/jira-lifecycle-plugin/config.yaml

---

Walkthrough

The Quay lifecycle configuration now targets quay-v5.0.0 for master and adds a redhat-5.0 branch targeting quay-v5.0.z with default validation enabled.

Changes

Quay lifecycle configuration

Layer / File(s)	Summary
Update Quay branch targets core-services/jira-lifecycle-plugin/config.yaml	The master branch now targets quay-v5.0.0. The redhat-5.0 branch targets quay-v5.0.z, depends on quay-v5.0.0, and enables default validation.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Suggested reviewers: ezio-auditore

🚥 Pre-merge checks | ✅ 15

✅ Passed checks (15 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the primary change: updating the Quay master version.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names	✅ Passed	The commit changes only config.yaml; its diff contains no Ginkgo tests or test-title constructs, so this check is not applicable.
Test Structure And Quality	✅ Passed	The commit changes only config.yaml and adds no Ginkgo test code, so the test-structure quality check is not applicable.
Microshift Test Compatibility	✅ Passed	The commit changes only core-services/jira-lifecycle-plugin/config.yaml and adds no Ginkgo tests or test constructs, so MicroShift test compatibility is not applicable.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	The PR changes only Jira lifecycle YAML configuration and adds no Ginkgo e2e tests, so SNO compatibility review does not apply.
Topology-Aware Scheduling Compatibility	✅ Passed	The commit changes only Jira lifecycle YAML version mappings; it adds no deployment manifests, operator code, controllers, or scheduling constraints.
Ote Binary Stdout Contract	✅ Passed	The PR changes only Jira YAML configuration; it adds no process-level binary code or stdout writes, and the modified YAML parses successfully.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	The commit changes only core-services/jira-lifecycle-plugin/config.yaml; it adds no Ginkgo e2e tests or network operations to assess.
No-Weak-Crypto	✅ Passed	The commit changes only Quay YAML version and branch metadata; the six added lines contain no listed weak algorithms, crypto implementation, or secret/token comparison.
Container-Privileges	✅ Passed	The PR changes only Jira branch-version configuration. Added lines contain no privileged, hostPID, hostNetwork, hostIPC, SYS_ADMIN, or allowPrivilegeEscalation settings.
No-Sensitive-Data-In-Logs	✅ Passed	The patch changes only Quay target-version YAML entries. It adds no logging code, credentials, tokens, passwords, PII, hostnames, or customer data.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bradmwilliams, jbpratt

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• core-services/jira-lifecycle-plugin/OWNERS [bradmwilliams]

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

[openshift-ci]

@jbpratt: all tests passed!

Full PR test history. Your PR dashboard.

Details

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.