Pin conda <25.7 to fix Windows build (#5176)#5176
Open
mdouze wants to merge 1 commit intofacebookresearch:mainfrom
Open
Pin conda <25.7 to fix Windows build (#5176)#5176mdouze wants to merge 1 commit intofacebookresearch:mainfrom
mdouze wants to merge 1 commit intofacebookresearch:mainfrom
Conversation
Contributor
|
@mdouze has exported this pull request. If you are a Meta employee, you can view the originating Diff in D103589106. |
meta-codesync
Bot
changed the title
mdouze
added a commit
to mdouze/faiss
that referenced
this pull request
May 4, 2026
Summary: 🤖 This diff was automatically generated by myclaw_faiss_monitor conda 25.7.0 was released today and broke conda-build 25.3.1's plugin registration. When conda 25.7.0 is installed, the `conda build` subcommand is no longer recognized, even though conda-build is installed in the same environment. Root cause: conda-build 25.3.1 was released before conda 25.7.0 and its plugin entry point is incompatible with conda 25.7.0's plugin loader. Fix: change `<=25.07` to `<25.7` to exclude conda 25.7.0 until conda-build is updated to support it. The previous constraint `<=25.07` treated 25.07 and 25.7.0 as equivalent (PEP 440), so conda 25.7.0 was pulled in. The new constraint `<25.7` pins below the broken release. Differential Revision: D103589106
Summary: 🤖 This diff was automatically generated by myclaw_faiss_monitor conda 25.7.0 was released today and broke conda-build 25.3.1's plugin registration. When conda 25.7.0 is installed, the `conda build` subcommand is no longer recognized, even though conda-build is installed in the same environment. Root cause: conda-build 25.3.1 was released before conda 25.7.0 and its plugin entry point is incompatible with conda 25.7.0's plugin loader. Fix: change `<=25.07` to `<25.7` to exclude conda 25.7.0 until conda-build is updated to support it. The previous constraint `<=25.07` treated 25.07 and 25.7.0 as equivalent (PEP 440), so conda 25.7.0 was pulled in. The new constraint `<25.7` pins below the broken release. Differential Revision: D103589106
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary:
🤖 This diff was automatically generated by myclaw_faiss_monitor
conda 25.7.0 was released today and broke conda-build 25.3.1's plugin
registration. When conda 25.7.0 is installed, the
conda buildsubcommandis no longer recognized, even though conda-build is installed in the same
environment. Root cause: conda-build 25.3.1 was released before conda 25.7.0
and its plugin entry point is incompatible with conda 25.7.0's plugin loader.
Fix: change
<=25.07to<25.7to exclude conda 25.7.0 until conda-buildis updated to support it.
The previous constraint
<=25.07treated 25.07 and 25.7.0 as equivalent(PEP 440), so conda 25.7.0 was pulled in. The new constraint
<25.7pinsbelow the broken release.
Differential Revision: D103589106