Thanks to visit codestin.com
Credit goes to github.com

Skip to content

🔒 🤖 CI Update lock files for array-api CI build(s) 🔒 🤖 #30930

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.

Sign up for GitHub

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

Jump to bottom
Closed
wants to merge 1 commit into from
Closed

🔒 🤖 CI Update lock files for array-api CI build(s) 🔒 🤖 #30930

wants to merge 1 commit into from

Conversation

scikit-learn-bot
Copy link
Contributor

Update lock files.

Note

If the CI tasks fail, create a new branch based on this PR and add the required fixes to that branch.

@scikit-learn-bot scikit-learn-bot force-pushed the auto-update-lock-files-array-api branch from 7ba89cd to d1a9c3c Compare March 3, 2025 05:03
@github-actions GitHub Actions
Copy link

github-actions bot commented Mar 3, 2025

✔️ Linting Passed

All linting checks passed. Your pull request is in excellent shape! ☀️

Generated for commit: d1a9c3c. Link to the linter CI: here

@betatim betatim mentioned this pull request Mar 3, 2025
Merged
@betatim
Copy link
Member

betatim commented Mar 3, 2025 •
edited
Loading

Superseeded by #30933

What is the normal way of dealing with this? Should I close this PR and then we merge #30933?

@thomasjpfan
Copy link
Member

Should I close this PR and then we merge #30933?

We normally link the new PR with this one with "Fixes #____" so merging the new one closes the old one.

REF: #30296

@betatim
Copy link
Member

betatim commented Mar 4, 2025 •
edited
Loading

If this PR had been green I'd have merged it myself, but I think for #30933 someone else should merge it? Ah no, in #30296 Guillaume ended up merging it himself after someone else gave a 👍. So I'll do that too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
Build / CI
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@scikit-learn-bot @betatim @thomasjpfan @web-flow