Skip to content

⬆️ Bump quantecon/actions from 0.12.0 to 0.21.0 - #667

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/quantecon/actions-0.21.0
Open

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/quantecon/actions-0.21.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 19, 2026

Copy link
Copy Markdown
Contributor

Bumps quantecon/actions from 0.12.0 to 0.21.0.

Release notes

Sourced from quantecon/actions's releases.

v0.21.0

Fixed

  • ⚠️ BREAKING build-lectures: the error-outputs check now checks a page taken from the execution cache. myst-nb 1.4.0 renders such a page from jupyter-cache's executed copy, but writes the notebook to _build/jupyter_execute without its outputs, and the check read only those. So it found no error output on a page the build did not execute itself: in a pull request's build over a restored execution cache, as templates/ci.yml sets up, and in a later build that rereads the pages, as html does after pdflatex in a book with parts. Wherever myst-nb looks in the cache for a page (a book that sets execute_notebooks: cache, for a page that no exclude pattern or mystnb setting keeps out of it), the check now finds the page's copy in the cache as myst-nb does, and checks its outputs. A page the cache has no copy of was executed by the build, and is checked as written. A cache that cannot be read leaves its pages unchecked, and is reported as an unreadable notebook is, failing the step with fail. The inputs, the output and the annotations are unchanged; the log's summary line now says how many notebooks came from the cache. The new harness job build-cache-error-guard executes a display-time error into the cache, then builds again with fail, once with --all over the same _build and once over the execution cache alone: both used to pass. A site whose cached pages carry such a traceback now fails its build: fix the cell, tag a deliberate one raises-exception, or set error-outputs: 'warn' while it does. (#322)

Documentation

  • Releases (CONTRIBUTING, Staged Releases): a release that changes what a build reports dispatches the lecture matrix at the candidate before v0 moves, and explains each red leg in the release PR. Once v0 has moved, the release dispatches the canary's cache.yml, ci.yml and publish.yml on its main, which fetch the actions through @v0 as a consumer does. The gate is dispatched outside the canary's Sunday schedules, with whose publish.yml it shares the pages concurrency group. TESTING.md describes the canary as QuantEcon/test-actions-lecture-intro#94 left it: templates/ at v0 on a Sunday schedule, with each deploy checked for its own build's marker file, which the release gate's deploy to the same GitHub Pages site cannot pass. It describes the canary watcher's new drift check too, which compares the canary's workflows with templates/ at v0, apart from the differences .github/canary-drift.yml declares. (#302, #310)
  • Which actions live here (ARCHITECTURE, README): this repository holds the lecture pipeline, released together at v0; any other action lives in its own action-<name> repository, which the README's new "Standalone actions" table lists. (#332)

v0.20.1

Fixed

  • build-jupyter-cache: when the jupyter build fails under -W --keep-going, the default extra-args, the failure issue now says that its command to reproduce the build exits 0 even when the build fails on warnings. sphinx-tojupyter ends the build with exit() and status 0 before Sphinx can fail it, so a local run of that command reported success, and only build-lectures' check of the warnings (#300) failed it in CI. The issue names the WARNING:, ERROR: and CRITICAL: lines that check counts, and says that without --keep-going the build stops at the first warning and exits 1, which a local run with jupyter-book 1.0.4post1 and sphinx-tojupyter 0.6.0 confirmed. The commands keep the flags the build had. The note appears only when the jupyter build failed and extra-args holds both flags, read as build-lectures' check reads them; without -W a warning fails nothing. bjc-alert checks the note for each set of flags, and runs build-lectures' own loop on them to check that the two agree. (#311)

v0.20.0

Changed

  • ⚠️ BREAKING build-lectures: a new nitpick input, 'true' by default, passes -n to jb build for every builder: Sphinx's nitpicky mode, which warns about every reference it cannot resolve, so that under -W one fails the build. The pdflatex and jupyter builders always passed -n, and now pass it through the input; nitpick: 'false' leaves it out. The html builder passed none, and now does: a site whose pages hold a reference that only nitpicky mode reports, such as a {py:func} naming a function no page documents, fails its html build until the reference is fixed. A -n that a caller also passes in extra-args does no harm: jb build takes it twice. #300's check of a jupyter build's warnings reads -W and --keep-going from extra-args, as before. build-jupyter-cache gets nitpick and extra-args too, with build-lectures' defaults, passes both to each of its builds, and refuses a nitpick other than 'true' or 'false' before setup. Its failure issue's commands to reproduce a build are built from them. It runs build-lectures@v0, so a caller pinned to an earlier build-jupyter-cache gets -n on its html cache build too, with no input to drop it, and moves to this release to set one. The new harness job build-nitpick shows an unresolved reference failing an html and a jupyter build with nitpick on, and passing both with it off; bjc-alert checks the commands and that each build is given both inputs. To migrate: fix each reference the build lists, accept its target in nitpick_ignore_regex in _config.yml, or set nitpick: 'false' on each build-lectures and build-jupyter-cache step while you do. (#97)

v0.19.0

Added

  • restore-gh-pages and templates/restore.yml: puts a GitHub Pages site back as one of the repository's releases holds it, without a build, from the archive, checksum and manifest that publish-gh-pages attaches on a tag. The action downloads the release's archive and checksum with gh, checks the archive's SHA-256 before anything is extracted, refuses an archive that holds anything but files and directories, and gives the extracted site as build-dir, with the commit it was built from as commit. It reads only the repository's own releases, needs only contents: read, and finds the archive by its tag unless asset-name is given. The template, run by hand on the default branch with the release's tag, hands the site to publish-gh-pages to deploy, in publish.yml's pages concurrency group. The next publish replaces the restored site. (#27)

Changed

  • Container images: sphinx-exercise moves from 1.2.1 to 1.2.2 in both images, which the full image pins and the lean image takes as its floor. The patch release writes a captioned figure inside an exercise or solution as \begin{figure}[H], as Sphinx does inside its own admonitions, so a PDF build no longer stops there with Not in outer par mode. HTML output is unchanged. Both images were smoke-tested before :latest moved, and the lecture matrix then passed on all eight legs. (#312)

Fixed

  • ⚠️ BREAKING build-lectures: a jupyter build under -W --keep-going, the default extra-args, now fails on a warning, as the other builders do. It used to pass every warning. sphinx-tojupyter's JupyterBuilder.finish() calls exit() with 0 inside Sphinx's build, before Sphinx turns the warnings that --keep-going counted into exit status 1. So jb build exited 0 whatever the build warned about, a cell that raised included. The release gate's staged-failure self-test showed it: only the error-output check caught the raised cell. The build step now keeps a copy of jb build's stderr, Sphinx's warning stream. For the jupyter builder, when jb build exits 0 with both -W and --keep-going in extra-args, it fails the step on any warning in it, and lists each in a log group. The failure report then prints the failed notebooks' tracebacks, as for any failed build. -W alone already failed at the first warning, and without -W nothing changes. build-jupyter-cache gets the same through build-lectures@v0; it builds jupyter first, so that build is the one that reads and executes the pages. The error-output check now tells a cell that raised, after which no code cell ran, from one whose output raised while it was displayed, after which one did. It says which in its annotation and in a Cause column in the step summary, where it used to say "The kernel reported this cell as successful" of both. The new harness job build-jupyter-warning-guard shows a clean jupyter build passing, a cell that raises failing the build step, the same warnings passing without -W, and the check's wording. The lecture matrix found one warning, in three lecture repositories: a tojupyter_static_file_path entry naming a directory the book does not have, which warns tojupyter_static_path entry … does not exist. Their pull requests drop that entry, and no other QuantEcon caller's jupyter build logs a warning. To migrate: fix each warning the build step lists, such as by dropping that entry, or set extra-args without -W for the jupyter build while you do. (#300)

v0.18.0

Added

  • preview-workers: a new action that previews a pull request on an existing Cloudflare Worker, as Cloudflare moves static sites from Pages to Workers. It uploads the built site as a new version of the Worker with wrangler versions upload --preview-alias pr-<number>, which never changes what the Worker serves in production, at https://pr-<number>-<worker-name>.<account-subdomain>.workers.dev, and comments on the pull request as preview-netlify and preview-cloudflare do, with a comment of its own. It has their trust gate, dispatch-alias, placeholder and outputs. deploy-url is built from the inputs and checked against wrangler's record of the upload: a wrong account-subdomain, or a Worker whose preview URLs are off, fails the job rather than post a link that cannot load. deployment-url is the version's own preview URL, which keeps showing that push. The wrangler config is generated for each run by the writer deploy-cloudflare uses, now in scripts/, with no change to deploy-cloudflare. The token is an account-owned API token scoped to the one Worker, which the chapter shows how to make. (#145)

Changed

  • Container images: builds of main outside the kept window are now deleted from GHCR. A new monthly workflow, prune-images.yml, keeps main's newest 10 builds and every version of the last 90 days, tagged or not, so every build of the last 90 days; the newest builds are the rollback targets. It keeps a dispatch from a branch for 14 days. It always keeps :latest, a pull request's candidates, every digest in .github/container-pins.txt, any version carrying a tag it does not own, and every manifest these list. Until now nothing was deleted: 338 versions of quantecon had built up, and 221 of quantecon-build. A workflow that pins an image by digest keeps working while that build is kept. To keep a pin for longer, add its digest to .github/container-pins.txt in a pull request, or have the version tagged with a name that does not end in -<7 hex digits>. The one pin known in QuantEcon, quantecon-build in the two theme test repositories, is in the file. A dispatch is a dry run unless told otherwise, a pull request that changes the pruner lists what it would delete, and a run with more than 50 versions of an image to delete deletes none. (#277)
  • preview-netlify, preview-cloudflare, deploy-cloudflare: through Dependabot's lockfile bump, preview-cloudflare and deploy-cloudflare pin wrangler 4.158.0, up from 4.156.1, and preview-netlify pins netlify-cli 27.16.2, up from 27.16.1. preview-workers ships with wrangler 4.158.0. The harness installs each from its lockfile and runs it. (#294)
  • publish-gh-pages: softprops/action-gh-release, which attaches the release assets, moves from 3.0.3 to 3.0.4, through Dependabot's bump. The patch release classifies GitHub API errors more safely. (#295)
  • Container images: quantecon-book-theme moves from 0.22.1 to 0.22.2 in both images, through Dependabot's bump. The patch release's dark-mode button is labelled "Toggle dark mode", and a site that sets no author no longer shows "Author name not set" in its page header. Both images were smoke-tested before :latest moved. (#293)

Documentation

  • Releases (CONTRIBUTING, Staged Releases): a release that changes an action passes the release gate before v0 moves. The gate is gate.yml in the canary, QuantEcon/test-actions-lecture-intro, dispatched on its main with the candidate, which it refuses unless it is reachable from main or a v* tag. It checks the candidate out and runs the actions from that checkout on a fixture whose image is pinned by digest and whose pages read nothing from the network: build-jupyter-cache cold with all three builders, its siblings at the candidate too; both cache restores; both previews and a GitHub Pages deploy, each checked for the candidate's build. It replaces the canary pull request and cache.yml dispatch that a staged release ran by hand, which now stage only what the gate does not reach: a preview's pull-request half, setup-environment outside a container, setup-latex, deploy-cloudflare, preview-workers, and a release's own scenarios. A red gate run from main assigns a release-gate issue in the canary to whoever dispatched it. TESTING.md describes the gate, and PLAN.md drops items 0a, 0b and 0d. (#135, #136)

v0.17.0

Added

  • setup-latex: a new action that installs TeX Live, or any apt packages, on a standard Ubuntu runner, from a cache of the downloaded .deb archives. A plain apt-get install downloads TeX Live from the runner's Ubuntu mirror on every run, 1.1 GB for the usual lecture list, and a slow mirror stalls that without ever failing: since September, 12 of 220 such steps in the lecture repositories took over 5 minutes, and the slowest ran for nearly 6 hours. The cache key hashes the packages installed on the host, so an exact hit installs the archives as local files with no apt-get update and no download. A fallback restore, as after a new runner image, downloads only what the cache lacks. It caches archives, not installed files, so dpkg runs TeX Live's maintainer scripts as before. download-timeout-minutes, 30 by default, stops a download that runs longer, and '0' sets no limit. The cache is saved after the install, except on an exact hit or from a tag. The 15 lecture repositories that inline their own apt-get install texlive-… step can switch with a one-step change, which the chapter shows. The work is in scripts/latex-packages.sh, for setup-environment's install-latex to share. (#224)

Changed

  • build-jupyter-cache, restore-jupyter-cache: the execution cache's key hashes the environment files too, as jupyter-cache-<hash of environment>-<hash of environment-update>-<hash of the lectures>-<run id>, and a restore falls back to jupyter-cache-<env>-<update>-, then jupyter-cache-<env>-: the build cache's fallbacks. It used to hash the lectures alone and fall back to any execution cache. .jupyter_cache checks each notebook against its code, but not against the packages that executed it, so a pull request that changed the environment file restored outputs made with the old packages, re-executed nothing, and passed. Now it misses and executes every lecture, as it does with the build cache. environment and environment-update apply to both cache types. A workflow that already restores cache-type: execution misses once after v0 moves, until its next cache build, and one that also sets fail-on-miss: 'true' should run its cache workflow once then; no QuantEcon workflow restores execution. The harness's new unit-exec-env-miss restores the seed's lectures under another environment file, and must miss. (#270)
  • templates/ci.yml, templates/publish.yml: both restore cache-type: 'execution', _build/.jupyter_cache alone, instead of the build cache. The build cache brings back what the last cache build made, including what the source has deleted since. Since #160 the restore removes its html, but a build that makes the notebooks or the PDF over it can still copy a removed lecture's notebook, or a deleted PDF, into the site. The execution cache leaves nothing of the kind, and is several times smaller, so a restore downloads less, and a pull request's save-cache stores less. The rest of _build saves no work: a fresh checkout makes Sphinx rewrite every page. A repository that copied an older template sets cache-type: 'execution' on the restore step of both. build-jupyter-cache still saves the build cache, since restore-jupyter-cache's default restores it; whether it stops, or becomes opt-in, goes with a later change of that default (review M3). (#270)
  • setup-environment: install-latex installs the LaTeX packages as setup-latex does, through the same script: from a cache of their downloaded archives, keyed on cache-version, the list and the packages installed on the host, with no apt-get update and no download on an exact hit. It used to download them from the runner's Ubuntu mirror on every run, which a slow mirror can stall for hours. A new output, latex-cache-hit, says which way they came. On a run that downloads, apt-get update and the download together are now stopped after 30 minutes, with no input to change it: a download that runs past 30 minutes now fails, where it used to finish slowly. No QuantEcon repository passes install-latex. build-jupyter-cache passes it for a pdflatex build in standard mode, and its three QuantEcon callers all run in a container. A repository that needs another limit can install LaTeX with setup-latex and its download-timeout-minutes instead. cache-version now keys the LaTeX cache too, so a bump also downloads the packages afresh. Each entry in the list must be an apt package name, so an option such as --no-install-recommends, which apt used to take from the file, now fails the job. The messages for a missing or empty list now name the file. (#224)
  • Container images: :latest moves only once the image it will point at has passed the smoke test. Until now the merge's own build pushed :latest directly, and test-container.yml tested it afterwards. That build is not the image its pull request tested: it rebuilds the changed layers, whose floating packages resolve again, and a dispatch or a direct push to main was tested by nothing. build-containers.yml now pushes only candidates, main-<sha> and one main-<date>-<time>-<sha> tag for the run, and calls test-container.yml on them twice, for the smoke test and for the size report. When every smoke test passes, a new promote job points :latest at the digest each build pushed, all the images together, with docker buildx imagetools create, through a new scripts/promote-image.sh. The script first checks that each candidate tag still resolves to the digest pushed, then that :latest does after the move, and the job's step summary has the digests pushed, promoted and replaced, with the rollback command. A failed smoke test or promotion leaves :latest where it was and opens the failure tracking issue. A failed size report alerts too, but cannot hold a promotion back, since it fails on the measurement, not the image. A cancelled run alerts only when no newer run has superseded it. On any branch but main the promotion is a dry run, and validate-containers.yml dry-runs it on each pull request's candidates, with a self-test of the script on every harness run. test-container.yml loses its workflow_run trigger and its own alert, now the build run's, and takes a checks input. The lecture matrix starts only after a run on main, since a branch's run moves nothing. :latest moves a few minutes later after a merge, by the smoke test's run time. Every main-* tag is kept as a rollback target. The sed tag lists in build-containers.yml are rewritten, so .github/actionlint.yaml and its ignores for them go. (#142)

Fixed

... (truncated)

Changelog

Sourced from quantecon/actions's changelog.

[0.21.0] - 2026-11-16

Documentation

  • Releases (CONTRIBUTING, Staged Releases): a release that changes what a build reports dispatches the lecture matrix at the candidate before v0 moves, and explains each red leg in the release PR. Once v0 has moved, the release dispatches the canary's cache.yml, ci.yml and publish.yml on its main, which fetch the actions through @v0 as a consumer does. The gate is dispatched outside the canary's Sunday schedules, with whose publish.yml it shares the pages concurrency group. TESTING.md describes the canary as QuantEcon/test-actions-lecture-intro#94 left it: templates/ at v0 on a Sunday schedule, with each deploy checked for its own build's marker file, which the release gate's deploy to the same GitHub Pages site cannot pass. It describes the canary watcher's new drift check too, which compares the canary's workflows with templates/ at v0, apart from the differences .github/canary-drift.yml declares. (#302, #310)
  • Which actions live here (ARCHITECTURE, README): this repository holds the lecture pipeline, released together at v0; any other action lives in its own action-<name> repository, which the README's new "Standalone actions" table lists. (#332)

Fixed

  • ⚠️ BREAKING build-lectures: the error-outputs check now checks a page taken from the execution cache. myst-nb 1.4.0 renders such a page from jupyter-cache's executed copy, but writes the notebook to _build/jupyter_execute without its outputs, and the check read only those. So it found no error output on a page the build did not execute itself: in a pull request's build over a restored execution cache, as templates/ci.yml sets up, and in a later build that rereads the pages, as html does after pdflatex in a book with parts. Wherever myst-nb looks in the cache for a page (a book that sets execute_notebooks: cache, for a page that no exclude pattern or mystnb setting keeps out of it), the check now finds the page's copy in the cache as myst-nb does, and checks its outputs. A page the cache has no copy of was executed by the build, and is checked as written. A cache that cannot be read leaves its pages unchecked, and is reported as an unreadable notebook is, failing the step with fail. The inputs, the output and the annotations are unchanged; the log's summary line now says how many notebooks came from the cache. The new harness job build-cache-error-guard executes a display-time error into the cache, then builds again with fail, once with --all over the same _build and once over the execution cache alone: both used to pass. A site whose cached pages carry such a traceback now fails its build: fix the cell, tag a deliberate one raises-exception, or set error-outputs: 'warn' while it does. (#322)

[0.20.1] - 2026-11-15

Fixed

  • build-jupyter-cache: when the jupyter build fails under -W --keep-going, the default extra-args, the failure issue now says that its command to reproduce the build exits 0 even when the build fails on warnings. sphinx-tojupyter ends the build with exit() and status 0 before Sphinx can fail it, so a local run of that command reported success, and only build-lectures' check of the warnings (#300) failed it in CI. The issue names the WARNING:, ERROR: and CRITICAL: lines that check counts, and says that without --keep-going the build stops at the first warning and exits 1, which a local run with jupyter-book 1.0.4post1 and sphinx-tojupyter 0.6.0 confirmed. The commands keep the flags the build had. The note appears only when the jupyter build failed and extra-args holds both flags, read as build-lectures' check reads them; without -W a warning fails nothing. bjc-alert checks

... (truncated)

Commits
  • d65e694 release: v0.21.0 (#334)
  • 0f81c35 docs: which actions live here, and where QuantEcon's other actions are (#332)
  • 08348a9 fix(build-lectures): check a page taken from the execution cache for error ou...
  • caf9ac2 ci(canary-watch): check the canary for drift from templates/ at v0 (#310) (#331)
  • c596497 ci(canary-watch): watch the canary's scheduled workflows from here (#302) (#328)
  • b68bc64 docs(plan): record #194's outcome: link checks stay per repository, #185 wait...
  • c21e481 docs(plan): v0 is on v0.20.1; #96 is parked (#195) (#325)
  • f7e98be release: v0.20.1 (#324)
  • d8eddc0 docs: a native pipeline's doctrees clear needs no counterpart (#98) (#323)
  • 48573a2 fix(build-jupyter-cache): say when the jupyter repro command exits 0 on warni...
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [quantecon/actions](https://github.com/quantecon/actions) from 0.12.0 to 0.21.0.
- [Release notes](https://github.com/quantecon/actions/releases)
- [Changelog](https://github.com/QuantEcon/actions/blob/main/CHANGELOG.md)
- [Commits](QuantEcon/actions@v0.12.0...v0.21.0)

---
updated-dependencies:
- dependency-name: quantecon/actions
  dependency-version: 0.21.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot Bot added dependencies Dependency or environment update (pip, conda, actions) github_actions Pull requests that update GitHub Actions code labels Nov 19, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Dependency or environment update (pip, conda, actions) github_actions Pull requests that update GitHub Actions code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants