build(env): adopt the PyMC 6.2 shared baseline - #454
Merged
Conversation
Sync the conda-forge core with dse-research-utils' canonical data/environment-core.yml, which moved the PyMC floor to 6.2.0 (PyMC 6.2 requires pytensor >=3.2.2,<3.3). The numba <=0.65.1, numpy <2.5 and pyarrow >=24.0.0 caps are unchanged and still required — pytensor 3.2.3 caps numba, numba 0.66.0 still pins numpy <2.5, and jaxlib's libabseil pin still holds libarrow at 24. Core floors: pandas 3.0.5, matplotlib 3.11.1, preliz 0.27.1, h5py 3.16.0, h5netcdf 1.8.1, python-graphviz 0.21. LRP add-ons: lightgbm 4.7.0, xarray 2026.7.0. Pip layer: ruff 0.16.1, setuptools 83.0.0, hatchling 1.31.0. pyproject floors are brought up to the same baseline, including the numpy <2.5 cap that the conda core carries, and dse-research-utils moves to v0.9.0. Verified with `conda create --dry-run` on linux-64 and osx-arm64 (solves to pymc 6.2.0 / pytensor 3.2.3) and with `dse-check-env environment.yml`. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
frankbuckley
marked this pull request as ready for review
July 31, 2026 10:20
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.
Note
Drafted by a LLM-based AI tool (Claude Code/Opus 5).
Adopts the refreshed shared baseline from dseinternational/research#79, which moves the canonical conda-forge core to PyMC 6.2.
pymc 6.2.0requirespytensor>=3.2.2,<3.3, so the floor moves6.1.0→6.2.0.What changed here
Core floors:
pandas 3.0.5,matplotlib 3.11.1,preliz 0.27.1,h5py 3.16.0,h5netcdf 1.8.1,python-graphviz 0.21. LRP add-ons:lightgbm 4.7.0,xarray 2026.7.0. Pip layer:ruff 0.16.1,setuptools 83.0.0,hatchling 1.31.0.pyproject.tomlfloors are brought up to the same baseline and now carry thenumpy<2.5cap the conda core has always had, so auvresolve and a conda solve agree.dse-research-utilsmoves tov0.9.0in both the pip layer and[tool.uv.sources].Why the caps did not move
Each was re-verified against live conda-forge metadata:
numba<=0.65.1pytensor-base 3.2.3still declaresnumba >=0.58,<=0.65.1, even though numba 0.66.0 is releasednumpy<2.5numpy <2.5too, so lifting the numba cap alone would not unlock numpy 2.5pyarrow>=24.0.0libarrow 25.0.0needslibabseil >=20260526; everyjaxlib 0.10.2build still pinslibabseil <20260108Verification
conda create --dry-runon bothlinux-64andosx-arm64: solves topymc 6.2.0/pytensor 3.2.3/numba 0.65.1/numpy 2.4.6/pyarrow 24.0.0.dse-check-env environment.yml— no drift against the updated canonical core.Blocked on the upstream tag
Opened as a draft. The pip layer installs
dse-research-utilsfromgit@v0.9.0, so CI here cannot pass until dseinternational/research#79 merges andv0.9.0is tagged.