docs(plan): every consumer is now on @v0 - #133
Merged
Merged
Conversation
Completes the record for the two consumer PRs cut today. The table said lecture-dp's move was "open" and still showed lecture-python.myst at @v0.8.0; both have merged, so all 11 call sites across the estate now track @v0 and no exact pins remain. Adds the reasoning under the table, because the argument came up twice in review and the counter-evidence is worth keeping. Pinning plus Dependabot is the obvious alternative and it was already configured — it surfaces the bump, but currency still depends on someone merging it, and lecture-python.myst#1000 sat open 13 days before being closed as superseded. The breaking-change risk pinning guards against is covered by the canary instead, which meets a bad release first on the same weekly cadence. Header also notes v0.11.1. 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 bookkeeping to reflect that all current consumer repositories now use the floating @v0 ref, and documents the rationale for preferring @v0 over exact tag pins (with the canary serving as the early warning for bad releases).
Changes:
- Refreshes the “Last updated” header to mention the latest releases and the completed consumer migrations to
@v0. - Updates the “Consumers in production” table so all listed consumers show
@v0and links the PRs that performed the migrations. - Adds a short rationale paragraph explaining why exact pinning + Dependabot was insufficient and why the canary mitigates breaking-change risk.
| Working plan for `QuantEcon/actions`: current state, prioritized backlog, dependency policy, and rollout status. | ||
|
|
||
| **Last updated:** 2026-08-07 — after the **v0.11.0** release, which is the first to carry both alerting fixes (#122, #127) to consumers: `build-jupyter-cache` reaches its siblings through the pinned `@v0` ref, so neither fix existed for any consumer until `v0` moved to this release. The backlog below is still the July 2026 review; individual items carry their own closure notes. | ||
| **Last updated:** 2026-08-07 — after the **v0.11.0** and **v0.11.1** releases and the move of every consumer to `@v0`, which is the first to carry both alerting fixes (#122, #127) to consumers: `build-jupyter-cache` reaches its siblings through the pinned `@v0` ref, so neither fix existed for any consumer until `v0` moved to this release. The backlog below is still the July 2026 review; individual items carry their own closure notes. |
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 bookkeeping for the two consumer PRs cut today. PLAN-only.
The consumers table had gone stale in this session's own edits: it recorded lecture-dp's move as "open" and still showed
lecture-python.mystat@v0.8.0. Both have since merged, so the table now reads@v0for all three consumers with links to the PRs that moved them.Verified against the repos rather than assumed — sweeping every workflow in the three consumer repos returns 11
quantecon/actions/*@v0call sites and zero exact pins.I also added a short paragraph under the table recording why, because the pinning argument came up in review on both consumer PRs and the counter-evidence is worth keeping somewhere durable. The obvious alternative — pin exactly, let Dependabot keep it current — was already configured in
lecture-python.mystand is not sufficient on its own: it surfaces the bump, but staying current still depends on a human merging it, and QuantEcon/lecture-python.myst#1000 sat open for 13 days before being closed as superseded. That is the same gap, one layer up, that left lecture-dp three releases behind and its weekly cache build un-alerted for ~2 months (#83). The breaking-change risk pinning guards against is covered instead by the canary, which runs the full chain against@v0on the same weekly cadence and so meets a bad release first.Header updated to mention v0.11.1 alongside v0.11.0.
🤖 Generated with Claude Code