Skip to content

OCPBUGS-79591: Prepare 1.3.4 release#163

Merged
openshift-merge-bot[bot] merged 2 commits into
openshift:masterfrom
alebedev87:prepare-release
May 11, 2026
Merged

OCPBUGS-79591: Prepare 1.3.4 release#163
openshift-merge-bot[bot] merged 2 commits into
openshift:masterfrom
alebedev87:prepare-release

Conversation

@alebedev87

@alebedev87 alebedev87 commented May 4, 2026 •
edited
Loading

Copy link
Copy Markdown
  • Fix the name label in Containerfile.externaldns to match product security metadata required by the check-labels release task
  • Bump the version label to 1.3.4

@alebedev87
Konflux: Change name label to match security labels
0e099eb 
`check-labels` task in release pipeline enforces the usage
of names which correspond to product security metadata.
Without this change, releasing to stage/prod is failing.
@openshift-ci openshift-ci Bot requested review from Thealisyed and bentito May 4, 2026 09:31
@alebedev87 alebedev87 changed the title Prepare 1.3.4 release OCPBUGS-79591: Prepare 1.3.4 release May 4, 2026
@openshift-ci-robot openshift-ci-robot added jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels May 4, 2026
@openshift-ci-robot

openshift-ci-robot commented May 4, 2026

Copy link
Copy Markdown

@alebedev87: This pull request references Jira Issue OCPBUGS-79591, which is invalid:

  • expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is MODIFIED instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

Summary

  • Fix the name label in Containerfile.externaldns to match product security metadata required by the check-labels release task
  • Bump the version label to 1.3.4

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-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels May 4, 2026
@openshift-ci-robot

openshift-ci-robot commented May 4, 2026

Copy link
Copy Markdown

@alebedev87: This pull request references Jira Issue OCPBUGS-79591, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (5.0.0) matches configured target version for branch (5.0.0)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
Details

In response to this:

  • Fix the name label in Containerfile.externaldns to match product security metadata required by the check-labels release task
  • Bump the version label to 1.3.4

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.

@alebedev87

alebedev87 commented May 4, 2026

Copy link
Copy Markdown
Author

/jira refresh

@openshift-ci-robot

openshift-ci-robot commented May 4, 2026

Copy link
Copy Markdown

@alebedev87: This pull request references Jira Issue OCPBUGS-79591, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (5.0.0) matches configured target version for branch (5.0.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
Details

In response to this:

/jira refresh

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.

@melvinjoseph86

melvinjoseph86 commented May 9, 2026

Copy link
Copy Markdown

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label May 9, 2026
grzpiotrowski
grzpiotrowski approved these changes May 11, 2026
View reviewed changes

@grzpiotrowski grzpiotrowski left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/approve

@openshift-ci

openshift-ci Bot commented May 11, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: grzpiotrowski

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:

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

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 11, 2026
@openshift-ci

openshift-ci Bot commented May 11, 2026

Copy link
Copy Markdown

@alebedev87: 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.

@openshift-merge-bot openshift-merge-bot Bot merged commit 1c18769 into openshift:master May 11, 2026
4 checks passed
@openshift-ci-robot

openshift-ci-robot commented May 11, 2026

Copy link
Copy Markdown

@alebedev87: Jira Issue OCPBUGS-79591: Some pull requests linked via external trackers have merged:

The following pull request, linked via external tracker, has not merged:

All associated pull requests must be merged or unlinked from the Jira bug in order for it to move to the next state. Once unlinked, request a bug refresh with /jira refresh.

Jira Issue OCPBUGS-79591 has not been moved to the MODIFIED state.

Details

In response to this:

  • Fix the name label in Containerfile.externaldns to match product security metadata required by the check-labels release task
  • Bump the version label to 1.3.4

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.

This was referenced May 11, 2026
Merged
Merged
Merged
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@bentito bentito Awaiting requested review from bentito
@Thealisyed Thealisyed Awaiting requested review from Thealisyed
1 more reviewer
@grzpiotrowski grzpiotrowski grzpiotrowski approved these changes
Reviewers whose approvals may not affect merge requirements

Assignees

@melvinjoseph86 melvinjoseph86

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@alebedev87 @openshift-ci-robot @melvinjoseph86 @grzpiotrowski