Skip to content

Conversation

@anik120
Copy link
Contributor

@anik120 anik120 commented Apr 16, 2025

Bumps github.com/go-jose/go-jose/v4 from 4.0.4 to 4.0.5.


updated-dependencies:

  • dependency-name: github.com/go-jose/go-jose/v4 dependency-type: indirect
    ...

Signed-off-by: dependabot[bot] support@github.com
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

@openshift-ci-robot openshift-ci-robot added jira/severity-moderate Referenced Jira bug's severity is moderate 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 Apr 16, 2025
@openshift-ci-robot
Copy link

@anik120: This pull request references Jira Issue OCPBUGS-51241, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
  • expected Jira Issue OCPBUGS-51241 to depend on a bug targeting a version in 4.19.0 and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

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.

This pull request references Jira Issue OCPBUGS-51243, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
  • expected Jira Issue OCPBUGS-51243 to depend on a bug targeting a version in 4.19.0 and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

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.

In response to this:

Bumps github.com/go-jose/go-jose/v4 from 4.0.4 to 4.0.5.


updated-dependencies:

  • dependency-name: github.com/go-jose/go-jose/v4 dependency-type: indirect
    ...

Signed-off-by: dependabot[bot] support@github.com
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.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.

@anik120
Copy link
Contributor Author

anik120 commented Apr 16, 2025

/jira refresh

@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 Apr 16, 2025
@openshift-ci-robot
Copy link

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

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.18.z) matches configured target version for branch (4.18.z)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-52928 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-52928 targets the "4.19.0" version, which is one of the valid target versions: 4.19.0
  • bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (bandrade@redhat.com), skipping review request.

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

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.18.z) matches configured target version for branch (4.18.z)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-52929 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-52929 targets the "4.19.0" version, which is one of the valid target versions: 4.19.0
  • bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (bandrade@redhat.com), skipping review request.

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.

@anik120 anik120 force-pushed the release-4.18-CVE-2025-27144 branch from c4c8722 to fdc1f56 Compare April 16, 2025 19:09
@anik120 anik120 changed the title OCPBUGS-51241,OCPBUGS-51243: Bump github.com/go-jose/go-jose/v4 from 4.0.4 to 4.0.5 (#1805) OCPBUGS-51241,OCPBUGS-51243: UPSTREAM: <drop>: Bump github.com/go-jose/go-jose/v4 from 4.0.4 to 4.0.5 (#1805) Apr 16, 2025
@anik120 anik120 changed the title OCPBUGS-51241,OCPBUGS-51243: UPSTREAM: <drop>: Bump github.com/go-jose/go-jose/v4 from 4.0.4 to 4.0.5 (#1805) OCPBUGS-51241,OCPBUGS-51243: Bump github.com/go-jose/go-jose/v4 from 4.0.4 to 4.0.5 (#1805) Apr 16, 2025
Bumps [github.com/go-jose/go-jose/v4](https://github.com/go-jose/go-jose) from 4.0.4 to 4.0.5.
- [Release notes](https://github.com/go-jose/go-jose/releases)
- [Changelog](https://github.com/go-jose/go-jose/blob/main/CHANGELOG.md)
- [Commits](go-jose/go-jose@v4.0.4...v4.0.5)

---
updated-dependencies:
- dependency-name: github.com/go-jose/go-jose/v4
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
@anik120 anik120 force-pushed the release-4.18-CVE-2025-27144 branch from fdc1f56 to 6e86cbd Compare April 16, 2025 19:18
@anik120 anik120 changed the title OCPBUGS-51241,OCPBUGS-51243: Bump github.com/go-jose/go-jose/v4 from 4.0.4 to 4.0.5 (#1805) OCPBUGS-51241,OCPBUGS-51243: Bump github.com/go-jose/go-jose/v4 from 4.0.4 to 4.0.5 Apr 16, 2025
@anik120
Copy link
Contributor Author

anik120 commented Apr 17, 2025

/test openshift-e2e-aws

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 17, 2025
@grokspawn
Copy link
Contributor

/approve

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 17, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: anik120, grokspawn

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

The pull request process is described here

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 Apr 17, 2025
@oceanc80
Copy link
Contributor

/label backport-risk-assessed

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Apr 17, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 17, 2025

@anik120: all tests passed!

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.

@bandrade
Copy link

/label cherry-pick-approved

@openshift-ci openshift-ci bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Apr 17, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit 9d64235 into openshift:release-4.18 Apr 17, 2025
9 checks passed
@openshift-ci-robot
Copy link

@anik120: Jira Issue OCPBUGS-51241: All pull requests linked via external trackers have merged:

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

Jira Issue OCPBUGS-51243: All pull requests linked via external trackers have merged:

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

In response to this:

Bumps github.com/go-jose/go-jose/v4 from 4.0.4 to 4.0.5.


updated-dependencies:

  • dependency-name: github.com/go-jose/go-jose/v4 dependency-type: indirect
    ...

Signed-off-by: dependabot[bot] support@github.com
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.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-bot
Copy link

[ART PR BUILD NOTIFIER]

Distgit: ose-olm-operator-controller
This PR has been included in build ose-olm-operator-controller-container-v4.18.0-202504171804.p0.g9d64235.assembly.stream.el9.
All builds following this will include this PR.

@anik120
Copy link
Contributor Author

anik120 commented Apr 29, 2025

/retitle OCPBUGS-51243: Bump github.com/go-jose/go-jose/v4 from 4.0.4 to 4.0.5

since openshift/operator-framework-catalogd#138 is doing the backport for catalogd for 4.18

@openshift-ci openshift-ci bot changed the title OCPBUGS-51241,OCPBUGS-51243: Bump github.com/go-jose/go-jose/v4 from 4.0.4 to 4.0.5 OCPBUGS-51243: Bump github.com/go-jose/go-jose/v4 from 4.0.4 to 4.0.5 Apr 29, 2025
@openshift-ci-robot
Copy link

@anik120: Jira Issue OCPBUGS-51243 is in an unrecognized state (Verified) and will not be moved to the MODIFIED state.

In response to this:

Bumps github.com/go-jose/go-jose/v4 from 4.0.4 to 4.0.5.


updated-dependencies:

  • dependency-name: github.com/go-jose/go-jose/v4 dependency-type: indirect
    ...

Signed-off-by: dependabot[bot] support@github.com
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. jira/severity-moderate Referenced Jira bug's severity is moderate 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

Development

Successfully merging this pull request may close these issues.