ci: Unpin micromamba again #28934
Merged
ci: Unpin micromamba again #28934
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
5362bf8 to
d4923e2
Compare
d4923e2 to
6363f55
Compare
tacaswell
approved these changes
Nov 22, 2024
|
@QuLogic can self-merge at his discretion. |
Upstream has updated their links, and the latest should have a fix for the error we were seeing.
6363f55 to
410c345
Compare
|
This looks good with the latest 2.0.4 release. |
|
Test failures are unrelated (this only touches AppVeyor). |
|
@meeseeksdev backport to v3.10.x |
meeseeksmachine
pushed a commit
to meeseeksmachine/matplotlib
that referenced
this pull request
Nov 26, 2024
ksunden
added a commit
that referenced
this pull request
Nov 27, 2024
…934-on-v3.10.x Backport PR #28934 on branch v3.10.x (ci: Unpin micromamba again)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR summary
Upstream has updated their links, and the latest should have a fix for the error we were seeing.
PR checklist