Skip to content

Conversation

@jenniferubah
Copy link
Contributor

(cherry picked from commit c1819ee)

Description

Update Orchestrator plugins to version 1.7.0.
Waiting to merge until plugins are available in npm production env.

PR acceptance criteria

Please make sure that the following steps are complete:

  • GitHub Actions are completed and successful
  • Unit Tests are updated and passing
  • E2E Tests are updated and passing
  • Documentation is updated if necessary (requirement for new features)
  • Add a screenshot if the change is UX/UI related

@openshift-ci
Copy link

openshift-ci bot commented Aug 15, 2025

Hi @jenniferubah. Thanks for your PR.

I'm waiting for a redhat-developer member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

@jenniferubah jenniferubah changed the title [DO NOT MERGE] Update Orchestrator plugins to version 1.7.0 Update Orchestrator plugins to version 1.7.0 Aug 15, 2025
@jenniferubah jenniferubah changed the title Update Orchestrator plugins to version 1.7.0 Feat - Update Orchestrator plugins to version 1.7.0 Aug 15, 2025
@jenniferubah jenniferubah changed the title Feat - Update Orchestrator plugins to version 1.7.0 Update Orchestrator plugins to version 1.7.0 Aug 15, 2025
@github-actions
Copy link
Contributor

@nickboldt nickboldt changed the title Update Orchestrator plugins to version 1.7.0 [release-1.7] Update Orchestrator plugins to version 1.7.0 Aug 15, 2025
@nickboldt nickboldt changed the title [release-1.7] Update Orchestrator plugins to version 1.7.0 chore: update Orchestrator plugins to version 1.7.0 [release-1.7] Aug 15, 2025
@nickboldt
Copy link
Member

See also #3286

@github-actions
Copy link
Contributor

This PR is stale because it has been open 7 days with no activity. Remove stale label or comment or this will be closed in 21 days.

@github-actions github-actions bot added the Stale label Aug 23, 2025
@jenniferubah jenniferubah force-pushed the cherry-pick-update-orchestrator-plugin-1.7.0 branch from c07137a to 4860f53 Compare September 11, 2025 21:46
@jenniferubah jenniferubah marked this pull request as ready for review September 11, 2025 21:46
@github-actions github-actions bot removed the Stale label Sep 12, 2025
@rm3l
Copy link
Member

rm3l commented Sep 12, 2025

/ok-to-test

@rm3l rm3l changed the title chore: update Orchestrator plugins to version 1.7.0 [release-1.7] chore: update Orchestrator plugins to version 1.7.1 [release-1.7] Sep 12, 2025
@rm3l
Copy link
Member

rm3l commented Sep 12, 2025

/cc @gazarenkov @nickboldt @rm3l

@github-actions
Copy link
Contributor

Copy link
Member

@rm3l rm3l left a comment

Choose a reason for hiding this comment

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

/lgtm

@openshift-ci
Copy link

openshift-ci bot commented Sep 12, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rm3l

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-merge-bot openshift-merge-bot bot merged commit ac850eb into redhat-developer:release-1.7 Sep 12, 2025
19 of 20 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants