You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Bump gufe / openfe / feflow runtime env pins to current latest stable (#512)
feflow 0.2.1 hit conda-forge and now pins gufe >=1.9.0,<2 and
openfe >=1.10.0,<2. The existing pins (gufe=1.6.1 / openfe=1.6.1 /
feflow=0.1.4 across the deployment envs, and gufe=1.7.1 / openfe=1.8.0
in test) leave callers unable to use feflow 0.2.1 against an
alchemiscale env.
Bump the trio to the latest mutually-compatible exact pins:
- gufe = 1.10.0 (satisfies openfe 1.11.1's gufe >=1.10.0,<1.11)
- openfe = 1.11.1 (satisfies feflow 0.2.1's openfe >=1.10.0,<2)
- feflow = 0.2.1 (latest stable)
Apply across the four runtime env files: test, server, compute,
client. devtools/conda-envs/docs.yml is intentionally unchanged --
the docs build runs sphinx 9's autodoc, which trips on the
`PositiveFloat | None` annotation in gufe >=1.8.0 (works with
pydantic v1 in gufe 1.3.0; pydantic v2 in gufe 1.10.0 makes
PositiveFloat an `Annotated[float, ...]` with no `__or__`). docs.yml
only needs gufe for intersphinx and type-hint resolution, so leaving
it at 1.3.0 keeps the docs build green; addressing the docs gufe
bump is a separate concern from this maintenance bump.
Extracted from PR #507 to unblock other inflight PRs needing the
newer dependency set.
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
0 commit comments