⬆️ Bump quantecon/actions from 0.8.0 to 0.11.1

[dependabot]

Bumps quantecon/actions from 0.8.0 to 0.11.1.

Release notes

Sourced from quantecon/actions's releases.

v0.11.1

preview-cloudflare now links the stable pr-{number}.{project}.pages.dev alias in PR comments instead of the per-deployment hash URL, so a reviewer can keep one tab open across a review — including every per-lecture deep link, which previously changed on every push.

@v0 now points at this release. Unlike the alerting fixes in v0.11.0, this one does not arrive via the build-jupyter-cache → sibling chain: the preview actions are called directly, so consumers pinning exact tags need v0.11.1 to pick it up.

New deployment-url output carries the immutable per-deployment URL, which the PR comment names in its Build Info block for anyone who needs to look at one specific revision.

---

Fixed

• preview-cloudflare: PR comments linked the per-deployment hash URL (https://b3a5c314.{project}.pages.dev) instead of the stable branch alias (https://pr-{number}.{project}.pages.dev), so every push to a PR produced a fresh set of links and reviewers had to scroll for the newest comment. The cost was larger than the headline URL: every per-lecture deep link in the comment carried the same hash, so a reviewer could not keep a tab open across a review. The alias is now constructed rather than parsed — pr-N is already alias-safe, so the URL is fully determined by inputs the action already holds, and no output parsing can go wrong. Note the README already documented the alias as the behaviour, so this brings the code in line with its own docs. A latent bug went with it: the old grep … | head -1 took whichever pages.dev URL came first, and wrangler prints the alias before the hash URL in some versions — so deploy-url silently returned the alias on one wrangler release and the hash on another. The per-deployment URL is still worth having, so it is now a separate deployment-url output (extracted by excluding the alias, not by position) and named in the comment's Build Info block for anyone who needs to look at one specific revision. Inputs in the deploy step also move from ${{ }} interpolation into env:, matching the discipline the comment step in the same file already followed. (#14)

v0.11.0

Failure alerting for the unattended weekly cache build now works on every path. Two independent gaps are closed: alerting never worked in container mode at all (#83), and a run that aborted before the builds skipped every guard including the alert (#123).

@v0 now points at this release. build-jupyter-cache calls setup-environment and build-lectures at the pinned @v0 ref, so these fixes only reach that chain now that v0 has moved. Consumers pinning exact tags need to bump to v0.11.0 to get them.

Requires issues: write on jobs using build-jupyter-cache with create-issue-on-failure: true — a missing permission is now a loud failure naming the fix, rather than silence.

---

Added

• build-jupyter-cache: upload-failure-reports input, default true, passed through to the inner build-lectures calls so a failed cache build uploads its reports/*.err.log tracebacks. Previously the failure issue told maintainers to "download the build artifact for detailed execution reports" while those reports were only reachable buried inside the full _build artifact — hundreds of MB including .jupyter_cache — and not at all when upload-artifact was off. The issue body now names the artifacts that were actually produced and gives per-builder reproduce commands matching build-lectures' real flags. The default deliberately differs from build-lectures' own false: that action is driven by a human watching a PR, this one runs unattended. (#83)
• CI: bjc-fail-guard harness job — a failing cache build must fail the step, report html-status=failure, and save no cache over the last good one. The failure path had no coverage at all, which is how three bugs accumulated on it. Issue filing itself stays out of the

... (truncated)

Changelog

Sourced from quantecon/actions's changelog.

[0.11.1] - 2026-08-07

Fixed

• preview-cloudflare: PR comments linked the per-deployment hash URL (https://b3a5c314.{project}.pages.dev) instead of the stable branch alias (https://pr-{number}.{project}.pages.dev), so every push to a PR produced a fresh set of links and reviewers had to scroll for the newest comment. The cost was larger than the headline URL: every per-lecture deep link in the comment carried the same hash, so a reviewer could not keep a tab open across a review. The alias is now constructed rather than parsed — pr-N is already alias-safe, so the URL is fully determined by inputs the action already holds, and no output parsing can go wrong. Note the README already documented the alias as the behaviour, so this brings the code in line with its own docs. A latent bug went with it: the old grep … | head -1 took whichever pages.dev URL came first, and wrangler prints the alias before the hash URL in some versions — so deploy-url silently returned the alias on one wrangler release and the hash on another. The per-deployment URL is still worth having, so it is now a separate deployment-url output (extracted by excluding the alias, not by position) and named in the comment's Build Info block for anyone who needs to look at one specific revision. Inputs in the deploy step also move from ${{ }} interpolation into env:, matching the discipline the comment step in the same file already followed. (#14)

[0.11.0] - 2026-08-07

Added

• build-jupyter-cache: upload-failure-reports input, default true, passed through to the inner build-lectures calls so a failed cache build uploads its reports/*.err.log tracebacks. Previously the failure issue told maintainers to "download the build artifact for detailed execution reports" while those reports were only reachable buried inside the full _build artifact — hundreds of MB including .jupyter_cache — and not at all when upload-artifact was off. The issue body now names the artifacts that were actually produced and gives per-builder reproduce commands matching build-lectures' real flags. The default deliberately differs from build-lectures' own false: that action is driven by a human watching a PR, this one runs unattended. (#83)
• CI: bjc-fail-guard harness job — a failing cache build must fail the step, report html-status=failure, and save no cache over the last good one. The failure path had no coverage at all, which is how three bugs accumulated on it. Issue filing itself stays out of the PR harness (it needs issues: write and would file real issues on every run); that belongs to the canary. (#83)

Changed

• CI: the action harness no longer uses paths: filters. A path filter suppresses creation of the workflow run, not just its jobs, so no check run is ever published for that commit and a required Action harness: all checks would sit "waiting for status to be reported" forever — GitHub's own guidance is to avoid requiring workflows that can be skipped. Demonstrated live: release PR #119 touched only CHANGELOG.md and GitHub reported "no checks reported on the branch". The workflow now always runs, and a new gate job decides relevance per-job (a job skipped by a conditional reports success to a required check). This is the prerequisite for making the harness a required check on main — issue #116 item 5, whose suggested paths-ignore companion workflow would not have worked, since paths-ignore is not the complement of paths and a mixed PR would fire both, producing two same-named check runs.

... (truncated)

Commits

• a388639 release: v0.11.1 (#132)
• 0a8e818 fix(preview-cloudflare): link the stable pr-N alias, not the deployment hash ...
• a363f24 docs(plan): record the v0.11.0 release and clear two stale backlog rows (#130)
• 86b7eee release: v0.11.0 (#128)
• 0b3ab33 fix(build-jupyter-cache): alert when the run aborts before the builds (#123) ...
• 7627b06 test(containers): make the container fixture able to fail (#108) (#125)
• 93149be ci: bump docker/login-action (#117)
• a7bb302 docs(plan): close the P0 alerting item, and correct its diagnosis (#126)
• 340da9a ci(harness): decide relevance in a gate job, not with paths: filters (#116 it...
• a5da9f3 fix(build-jupyter-cache): make container-mode failure alerting actually work ...
• Additional commits viewable in compare view

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)

[netlify]

✅ Deploy Preview for lustrous-melomakarona-3ee73e ready!

Name	Link
🔨 Latest commit	e0777ce
🔍 Latest deploy log	https://app.netlify.com/projects/lustrous-melomakarona-3ee73e/deploys/6a7a3ee4762eef000848f3fa
😎 Deploy Preview	https://deploy-preview-371--lustrous-melomakarona-3ee73e.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.