Skip to content

[8.19] (backport #15930) ci: enable windows-2025 #17635

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jul 15, 2025
Merged

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Jul 14, 2025

Motivation/summary

Checklist

For functional changes, consider:

  • Is it observable through the addition of either logging or metrics?
  • Is its use being published in telemetry to enable product improvement?
  • Have system tests been added to avoid regression?

How to test these changes

In the CI.

Related issues

Part of #15904


This is an automatic backport of pull request #15930 done by Mergify.

* ci: enable windows-2025

* revert

* Update .github/workflows/ci.yml

(cherry picked from commit 232a6ca)
@mergify mergify bot added the backport label Jul 14, 2025
@mergify mergify bot requested a review from a team as a code owner July 14, 2025 15:46
@mergify mergify bot added the backport label Jul 14, 2025
@mergify mergify bot assigned v1v Jul 14, 2025
Copy link
Contributor

🤖 GitHub comments

Expand to view the GitHub comments

Just comment with:

  • run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)

mergify bot added a commit that referenced this pull request Jul 14, 2025
Copy link
Contributor Author

mergify bot commented Jul 14, 2025

This pull request has been removed from the queue for the following reason: pull request manually updated.

The pull request #17635 has been manually updated.

You can check the last failing draft PR here: #17641.

If you want to requeue this pull request, you can post a @mergifyio requeue comment.

@kruskall
Copy link
Member

@Mergifyio requeue

Copy link
Contributor Author

mergify bot commented Jul 14, 2025

requeue

✅ The queue state of this pull request has been cleaned. It can be re-embarked automatically

mergify bot added a commit that referenced this pull request Jul 14, 2025
@kruskall
Copy link
Member

@Mergifyio dequeue

@kruskall
Copy link
Member

@Mergifyio refresh

@kruskall
Copy link
Member

@Mergifyio queue

Copy link
Contributor Author

mergify bot commented Jul 14, 2025

This pull request has been removed from the queue for the following reason: pull request dequeued.

Pull request #17635 has been dequeued by a dequeue command.

You can check the last failing draft PR here: #17647.

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.
If you do update this pull request, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

Copy link
Contributor Author

mergify bot commented Jul 14, 2025

dequeue

✅ The pull request has been removed from the queue default

Copy link
Contributor Author

mergify bot commented Jul 14, 2025

refresh

✅ Pull request refreshed

Copy link
Contributor Author

mergify bot commented Jul 14, 2025

queue

✅ The pull request has been merged automatically

The pull request has been merged automatically at 89da692

mergify bot added a commit that referenced this pull request Jul 14, 2025
@kruskall kruskall closed this Jul 14, 2025
@kruskall kruskall reopened this Jul 14, 2025
@mergify mergify bot mentioned this pull request Jul 15, 2025
2 tasks
mergify bot added a commit that referenced this pull request Jul 15, 2025
@mergify mergify bot merged commit 89da692 into 8.19 Jul 15, 2025
27 checks passed
@mergify mergify bot deleted the mergify/bp/8.19/pr-15930 branch July 15, 2025 15:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants