deps: bump the conda-major group across 2 directories with 2 updates - #87
Closed
dependabot[bot] wants to merge 1 commit into
Closed
dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
mmcky
added a commit
that referenced
this pull request
Jul 2, 2026
The previous PLAN.md was a migration-plan snapshot frozen in February 2026: Phase 1 (lecture-dp) has since shipped and runs the full chain in production at v0.8.0, and a July 2026 deep technical review of all actions, containers, workflows, docs, and open issues/PRs produced a concrete backlog that had no home. This rewrite makes PLAN.md the single forward-looking plan: - Current state: v0.8.0, the June 2026 hardening pass, and a verified consumer table (lecture-dp full chain, lecture-python.myst previews) - Prioritized backlog P0-P3 from the review, e.g. the container-mode gh-CLI alerting gap (see #83), missing failure-report artifacts, Dependabot conda-group drift (see #28, PRs #86/#87), and the preview-cloudflare alias URL (see #14) - Dependency policy: the Anaconda-baseline "bump as a set" invariant and the hold on PRs #86/#87 - Open-issues disposition table from the triage - Updated rollout status, compressing the completed February gap analysis to its two remaining RunsOn verification items All factual claims were verified against the current tree and live consumer repos. Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
Bumps the conda-major group with 1 update in the /containers/quantecon directory: anaconda. Bumps the conda-major group with 1 update in the /containers/quantecon-build directory: pandas. Updates `anaconda` from 2025.12 to 2026.06 Updates `pandas` from 2.3.3 to 3.0.3 --- updated-dependencies: - dependency-name: anaconda dependency-version: '2026.06' dependency-type: direct:production dependency-group: conda-major - dependency-name: pandas dependency-version: 3.0.3 dependency-type: direct:production update-type: version-update:semver-major dependency-group: conda-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/conda/containers/quantecon/conda-major-1e895faf34
branch
from
July 7, 2026 05:24
b8efd9b to
46216dd
Compare
Contributor
|
Closing — anaconda 2025.12→2026.06 and pandas 2.3.3→3.0.3 are exactly the upgrade to defer to a coordinated bump of the lecture repos + both containers: pandas 3.0 is a major that's unvalidated across the lectures, and this would diverge the containers from the source repos (all still on 2025.12). It also leaves the lean image incoherent — pandas 3.0.3 sitting next to a 2025.12-era numpy 2.3.5. #95 adds anaconda + pandas (and the rest of the pinned stack) to Dependabot's ignore list so this holds until a deliberate, coordinated upgrade. |
Contributor
Author
|
This pull request was built based on a group rule. Closing it will not ignore any of these versions in future pull requests. To ignore these dependencies, configure ignore rules in dependabot.yml |
dependabot
Bot
deleted the
dependabot/conda/containers/quantecon/conda-major-1e895faf34
branch
July 8, 2026 06:00
mmcky
added a commit
that referenced
this pull request
Jul 8, 2026
All flagship lecture repos now pin `anaconda=2026.06`, so move the containers to match — keeping them reproducible and consistent with the source repos and with each other (the #28 / PR #84 rationale, now retargeted from 2025.12 to 2026.06): - Full `quantecon` image: anaconda 2025.12 -> 2026.06. - Lean `quantecon-build` image: repin the individual scientific stack to the exact anaconda=2026.06 linux-64 py313 (MKL) versions — numpy 2.4.6, scipy 1.17.1, pandas 3.0.3, matplotlib 3.10.9, numba 0.65.1, networkx 3.6.1, statsmodels 0.14.6, scikit-learn 1.8.0 (seaborn 0.13.2 / sympy 1.14.0 unchanged). Resolved via `conda search anaconda=2026.06 --info`; linux-64 keeps MKL as the default BLAS, so the existing mkl pins stand. These are the deliberate coordinated-bump versions — not Dependabot's latest, which overshoot the baseline (numpy 2.5.0, scipy 1.18.0, etc.). Also add the pinned stack + `anaconda` to the Dependabot conda `ignore` list so it holds at 2026.06 until the next coordinated bump, instead of being drifted piecemeal (the #86 / #87 PRs this supersedes). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
mmcky
added a commit
that referenced
this pull request
Jul 8, 2026
All flagship lecture repos now pin `anaconda=2026.06`, so move the containers to match — keeping them reproducible and consistent with the source repos and with each other (the #28 / PR #84 rationale, now retargeted from 2025.12 to 2026.06): - Full `quantecon` image: anaconda 2025.12 -> 2026.06. - Lean `quantecon-build` image: repin the individual scientific stack to the exact anaconda=2026.06 linux-64 py313 (MKL) versions — numpy 2.4.6, scipy 1.17.1, pandas 3.0.3, matplotlib 3.10.9, numba 0.65.1, networkx 3.6.1, statsmodels 0.14.6, scikit-learn 1.8.0 (seaborn 0.13.2 / sympy 1.14.0 unchanged). Resolved via `conda search anaconda=2026.06 --info`; linux-64 keeps MKL as the default BLAS, so the existing mkl pins stand. These are the deliberate coordinated-bump versions — not Dependabot's latest, which overshoot the baseline (numpy 2.5.0, scipy 1.18.0, etc.). Also add the pinned stack + `anaconda` to the Dependabot conda `ignore` list so it holds at 2026.06 until the next coordinated bump, instead of being drifted piecemeal (the #86 / #87 PRs this supersedes). Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
8 tasks
mmcky
added a commit
that referenced
this pull request
Aug 7, 2026
…95 Verified rather than assumed: all eleven science-stack packages plus anaconda are in .github/dependabot.yml under `ignore` with no `update-types`, so every update type is blocked, and #95 corrected the header comment in the same change. The old comment claimed a date-pin meant the metapackage "stays put", which is the misconception that allowed #86/#87 to be proposed in the first place. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
mmcky
added a commit
that referenced
this pull request
Aug 7, 2026
…ws (#130) * docs(plan): record the v0.11.0 release and clear two stale backlog rows Current state: latest release is v0.11.0 and `@v0` points at it, which is the fact that matters — build-jupyter-cache reaches setup-environment and build-lectures through the pinned `@v0` ref, so neither alerting fix existed for any consumer until the tag moved. Also notes what the release unblocks: whether an issue is actually *filed* is the half the in-repo harness structurally cannot cover, so the canary is the only place it runs, and it only began running it when v0 moved. Two backlog rows referenced PRs that are long since resolved — #86/#87 closed and the stack moved as a set in #95, #90 merged, #88 closed. The repo has no open PRs at all. Both rows are struck rather than deleted, matching how the other closed items are recorded here. Consumers table: lecture-dp is moving from @v0.8.0 to @v0 in lecture-dp#52. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> * docs(plan): close backlog item 3 — the conda ignore entries landed in #95 Verified rather than assumed: all eleven science-stack packages plus anaconda are in .github/dependabot.yml under `ignore` with no `update-types`, so every update type is blocked, and #95 corrected the header comment in the same change. The old comment claimed a date-pin meant the metapackage "stays put", which is the misconception that allowed #86/#87 to be proposed in the first place. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> * docs(plan): drop a stranded preposition, close a multi-sentence bullet Two style fixes from Copilot on #130, taken selectively. Line 16 gets its missing terminal period: that bullet carries internal sentence-ending periods and then stops, so it was inconsistent with itself. Line 13 loses the stranded preposition ("which @v0 now points at" → "and @v0 points to it"). It was not the incomplete sentence the review took it for, but it read awkwardly at the end of a bullet. Deliberately NOT adding terminal periods to the single-fragment bullets: lines 14 and 15 predate this PR and end without one, so no-period is the convention here and line 13 would have become the odd one out. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
mmcky
added a commit
that referenced
this pull request
Aug 11, 2026
Five stale facts, all overtaken by v0.11.1 (#131/#132): - latest release read v0.11.0 - backlog item 5 (#14, the Cloudflare alias URL) was still listed as open although #131 shipped it; its disposition row still said "Still valid" - the dependency policy still pinned the baseline to anaconda=2025.12, four months after #95 migrated both images to 2026.06 - the rollout section still showed lecture-dp and lecture-python.myst on @v0.8.0, contradicting the "every consumer now tracks @v0" line above it The disposition table covered 8 issues while 21 are open, so it was no longer usable as a status view. Adds a second table for everything opened after the July review, including #135. Item 3's "=2025.12" is left as-is: it narrates the misconception that produced #86/#87, not the current baseline. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
mmcky
added a commit
that referenced
this pull request
Aug 11, 2026
#137 corrected the consumers table and added release gating; this clears what it did not touch, found while triaging all 20 open issues: - backlog item 5 (#14, the Cloudflare alias URL) was still listed as open although #131 shipped it in v0.11.1; its disposition row still read "Still valid" - the dependency policy still pinned the baseline to anaconda=2025.12, a month after #95 migrated both images to 2026.06 - rollout Phase 1 still put lecture-dp on @v0.8.0, contradicting the consumers table above it The disposition table covered 8 issues while 23 are open, so it had stopped working as a status view. Adds a second table for everything opened after the July review. Item 3's "=2025.12" is left alone: it narrates the misconception that produced #86/#87, not the current baseline. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
mmcky
added a commit
that referenced
this pull request
Aug 11, 2026
…ker (#139) #137 corrected the consumers table and added release gating; this clears what it did not touch, found while triaging all 20 open issues: - backlog item 5 (#14, the Cloudflare alias URL) was still listed as open although #131 shipped it in v0.11.1; its disposition row still read "Still valid" - the dependency policy still pinned the baseline to anaconda=2025.12, a month after #95 migrated both images to 2026.06 - rollout Phase 1 still put lecture-dp on @v0.8.0, contradicting the consumers table above it The disposition table covered 8 issues while 23 are open, so it had stopped working as a status view. Adds a second table for everything opened after the July review. Item 3's "=2025.12" is left alone: it narrates the misconception that produced #86/#87, not the current baseline. Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
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.
Bumps the conda-major group with 1 update in the /containers/quantecon directory: anaconda.
Bumps the conda-major group with 1 update in the /containers/quantecon-build directory: pandas.
Updates
anacondafrom 2025.12 to 2026.06Updates
pandasfrom 2.3.3 to 3.0.3