chore(ci): track quantecon/actions at the floating @v0 - #1029
Merged
Conversation
Both call sites move from @v0.8.0 to @v0, the reference CONTRIBUTING recommends for consumers. This is the last QuantEcon repo still on an exact pin. Worth being clear that this changes almost nothing today. Diffing v0.8.0 against v0.11.1 for the two actions this repo uses: preview-netlify is byte-for- byte unchanged, and publish-gh-pages differs by one line — a SHA bump of the third-party softprops/action-gh-release. The only BREAKING change in that span was to restore-jupyter-cache, which this repo does not use. So the value is entirely prospective. lecture-dp made the case: it sat three releases behind on exact pins and ran its unattended weekly build for roughly two months with failure alerting that had never worked, because the pin had to be bumped by hand to deliver the fix. Nothing here is unattended in the same way, but the drift mechanism is identical and there is no reason to keep it. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Contributor
There was a problem hiding this comment.
Pull request overview
Updates this repository’s GitHub Actions workflow call sites to follow QuantEcon’s recommended versioning strategy by switching quantecon/actions from an exact v0.8.0 pin to the floating @v0 tag, reducing manual maintenance to receive upstream fixes.
Changes:
- Update
quantecon/actions/publish-gh-pagesreference in the publish workflow from@v0.8.0to@v0. - Update
quantecon/actions/preview-netlifyreference in the CI workflow from@v0.8.0to@v0.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| .github/workflows/publish.yml | Switch publish-gh-pages action reference to the floating @v0 tag. |
| .github/workflows/ci.yml | Switch preview-netlify action reference to the floating @v0 tag. |
📖 Netlify Preview Ready!Preview URL: https://pr-1029--sunny-cactus-210e3e.netlify.app Commit: Build Info
|
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.
Moves both
quantecon/actionscall sites from@v0.8.0to the floating@v0, the reference CONTRIBUTING recommends for consumers. This is the last QuantEcon repo still on an exact pin.This changes almost nothing today
Worth stating plainly, because the diff looks more consequential than it is. Comparing
v0.8.0againstv0.11.1for the two actions this repo actually uses:preview-netlifypublish-gh-pagessoftprops/action-gh-releaseThe only⚠️ BREAKING change in that span was to
restore-jupyter-cache, which this repo does not use. So there is no behaviour change to review here and nothing to verify beyond CI staying green.Why do it then
The value is entirely prospective, and
lecture-dpjust made the case for it. That repo sat three releases behind on exact pins and ran its unattended weekly cache build for roughly two months with failure alerting that had never worked — because the fix could only arrive by someone remembering to bump a pin. A pin that must be bumped by hand in order to deliver a fix has the same failure mode as the missing fix.Nothing in this repo is unattended in quite that way, so the risk here is lower. But the drift mechanism is identical, and with the rest of the estate on
@v0there is no reason to keep the one exception.The usual counter —⚠️ BREAKING markers with migration notes in the changelog.
0.xminors may break — is covered bytest-actions-lecture-intro, which runs the full chain against@v0and meets a bad release first, and by🤖 Generated with Claude Code