Skip to content

relax hydra-core pin from ==1.3 to >=1.3,<2#257

Open
korbonits wants to merge 1 commit into
SalesforceAIResearch:mainfrom
korbonits:relax-hydra-core-pin
Open

relax hydra-core pin from ==1.3 to >=1.3,<2#257
korbonits wants to merge 1 commit into
SalesforceAIResearch:mainfrom
korbonits:relax-hydra-core-pin

Conversation

@korbonits
Copy link
Copy Markdown

Summary

  • Changes hydra-core==1.3hydra-core>=1.3,<2 in pyproject.toml

Why

The exact ==1.3 pin makes uni2ts incompatible with any package that requires hydra-core>=1.3.1 or >=1.3.2. A concrete example: sam2 (Meta's Segment Anything Model 2) requires hydra-core>=1.3.2, so the two packages cannot be installed in the same environment today.

The 1.3.x series has only patch releases between 1.3.0 and 1.3.2. There are no breaking changes in those patches — they're bug fixes and minor improvements to the Hydra config system. Nothing in uni2ts should be affected.

What was changed

-  "hydra-core==1.3",
+  "hydra-core>=1.3,<2",

The <2 upper bound is conservative — it prevents any hypothetical hydra-core 2.0 from being pulled in before this project has been tested against it.

Test plan

  • Verify existing tests still pass with hydra-core==1.3.2 installed
  • Confirm pip install uni2ts sam2 resolves without conflict after this change

The exact pin  blocks co-installation with any package
that requires hydra-core>=1.3.1 or >=1.3.2 (e.g. sam2, which needs
>=1.3.2). The 1.3.x line has only patch releases; there are no breaking
changes between 1.3.0 and 1.3.2.

Using >=1.3,<2 allows resolver flexibility within the stable 1.x series
without pulling in any hypothetical 2.0 that may have breaking changes.
@salesforce-cla
Copy link
Copy Markdown

Thanks for the contribution! Before we can merge this, we need @korbonits to sign the Salesforce Inc. Contributor License Agreement.

@korbonits
Copy link
Copy Markdown
Author

Signed it!

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.

1 participant