⬆️ Bump anaconda from 2026.06 to 2026.07 - #48
Conversation
Rolling monthly bump of the conda env pin. Opened by hand rather than by Dependabot: this repo's weekly Dependabot slot had not yet fired for the 2026.07 release, and the rest of the Python lecture family has already been validated and merged. Validated the same way as the rest of the family — by dispatching `cache.yml` on this branch for a full fresh `jb build lectures -W --keep-going` under the new env. See QuantEcon/workspace-lectures#21 for the cross-repo status. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
Updates the repository’s Conda environment definition to the next monthly Anaconda metapackage release, keeping the lecture build/runtime environment aligned with the rest of the Python lecture family’s 2026.07 sweep.
Changes:
- Bump
anacondametapackage pin from2026.06to2026.07inenvironment.yml.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
✅ Validated — safe to merge. Validated by dispatching Result: run 29708296238 completed success, with the build job running 38m55s — a full execution pass, not a cache reuse. I also grepped Note: the Cross-repo status for this sweep is tracked in QuantEcon/workspace-lectures#21. |
Rolling monthly bump of the conda env pin
anaconda=2026.06 → 2026.07.Why this is hand-authored rather than a Dependabot PR
Dependabot assigns each repo a fixed weekly slot, and this repo's slot had not yet fired for the 2026.07 release. The rest of the Python lecture family has already been bumped, validated and merged, so this opens the PR by hand to finish the sweep rather than waiting several more days.
If Dependabot later opens its own PR for the same bump it will not recognise this one, so that duplicate should be closed (as happened with lecture-python-advanced.myst#349 during the 2026.06 round).
Validation
The
pull_requestCI check is not a meaningful test of an env-only bump — it downloads themainbuild-cache artifact and reuses the cached notebook outputs, so it skips re-executing the notebooks under the new env entirely. A green check there proves nothing about the upgrade.The canonical signal is a
cache.ymldispatch on this branch, which does a full freshjb build lectures -W --keep-going(warnings→errors) executing every notebook under 2026.07. I have dispatched that run and will report the result here.Known 2026.07 breakage — pre-checked
The one regression found so far in this sweep is that anaconda 2026.07's matplotlib removes the long-deprecated
matplotlib.cm.get_cmap, which raisesImportErrorat import time and kills the whole notebook (hit lecture-python-introlaffer_adaptive.md, fixed in QuantEcon/lecture-python-intro#798). I grepped this repo'slectures/for that pattern before opening — no hits.Cross-repo status for this sweep is tracked in QuantEcon/workspace-lectures#21.