docs(plan): record the v0.11.0 release and clear two stale backlog rows - #130
Merged
Merged
Conversation
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>
…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>
Contributor
There was a problem hiding this comment.
Pull request overview
Updates PLAN.md to reflect the v0.11.0 release state and to clean up stale backlog entries, keeping the project plan aligned with current rollout and repository status.
Changes:
- Record v0.11.0 as the latest release and note that
@v0now points at it, including why that matters for downstream consumers. - Update the consumers table to reflect
lecture-dpmoving from a pinned tag to floating@v0. - Mark two outdated backlog items as resolved (struck through) rather than leaving them as active work.
Suppressed comments (1)
PLAN.md:16
- This bullet is missing a final period, leaving the last sentence fragment ("...when
v0moved to v0.11.0") dangling. Adding terminal punctuation will make the paragraph read cleanly.
- **August 2026 alerting pass** — unattended cache-build failures now reach the tracker on every failure path: during the builds (#83, #122) and before them (#123, #127). Shipped in v0.11.0. The half neither fix can prove in-repo is whether an issue is *actually filed* — that needs `issues: write` and would open real issues on every PR run — so the canary is now the only place it is exercised, and it only started exercising it when `v0` moved to v0.11.0
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>
8 tasks
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
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.
Follow-up to the v0.11.0 release (#128). PLAN-only.
Current state now records that the latest release is
v0.11.0and that@v0points at it. That second half is the load-bearing part:build-jupyter-cachereachessetup-environmentandbuild-lecturesthrough the pinned@v0ref, so neither alerting fix existed for any consumer until the tag moved — the release is what makes #122 and #127 real rather than merely merged.It also records what the release unblocks. Whether an issue is actually filed is the half the in-repo harness structurally cannot cover — it needs
issues: writeand would open real issues on every PR run — so the canary is the only place that path runs, and it only began running it whenv0moved to v0.11.0.Two backlog rows were stale, which I missed in the earlier PLAN pass: row 4 ("Hold PRs #86 and #87") and row 13 ("Merge safe Dependabot PRs #90 and #88") all reference PRs that are long since closed or merged, and the container stack has since moved as one coordinated set to the anaconda 2026.06 baseline in #95. There are currently no open PRs in this repo at all. Both rows are struck through rather than deleted, matching how every other closed item is recorded in this file. The standing policy row 4 existed to enforce is unchanged and lives in Dependency policy; backlog item 3 is what stops Dependabot re-proposing the same drift.
Consumers table notes lecture-dp moving from
@v0.8.0to floating@v0in QuantEcon/lecture-dp#52.🤖 Generated with Claude Code