⬆️ Bump QuantEcon/action-link-checker from 1.1.0 to 1.2.0

[dependabot]

Bumps QuantEcon/action-link-checker from 1.1.0 to 1.2.0.

Release notes

Sourced from QuantEcon/action-link-checker's releases.

v1.2.0 — the action's steps move to Node 24

Moves the action's own steps onto Node 24. Node 20 reached end-of-life on 2026-04-30. No input, output or script changes, so a workflow pinned to QuantEcon/action-link-checker@v1 keeps working as it is, and v1 now follows this release.

Node 24

actions/github-script moves from v7 to v9 (three steps) and actions/upload-artifact from v4 to v7, both of which run on Node 24.

GitHub-hosted runners already meet the one new requirement. A self-hosted runner needs v2.327.1 or later to run the new pins.

This repository's own CI

These changes affect contributors to the action, not workflows that use it.

CI now serves its fixtures from 127.0.0.1, so no gating step depends on the public internet. A clean page, a followed redirect, a reported error status and that status silenced by silent-codes are each asserted end to end against responses under our control. The scans of good-links.html and broken-links.html remain as informational smoke that cannot turn CI red, and they no longer post a comment on pull requests, since their findings are true by construction.

A new check-own-docs job renders this repository's Markdown and checks the links in it. It is the only job that comments on a pull request, and only when a link we publish is reported broken; it runs with silent-codes: '0,403,503' so a transient failure stays quiet. On its first run it found the README's Marketplace badge linking to a page that returns 404 (the action was never published there), which is fixed.

CI itself moves to actions/checkout v7 and actions/setup-python v7, with a grouped weekly Dependabot config for GitHub Actions so the pins do not fall behind again.

Pinned to an exact version?

A workflow pinned to @v1.1.0 rather than @v1 stays on Node 20 until it moves to @v1.2.0. Dependabot proposes that bump where it is configured for GitHub Actions.

Full changelog: https://github.com/QuantEcon/action-link-checker/blob/v1.2.0/CHANGELOG.md

Changelog

Sourced from QuantEcon/action-link-checker's changelog.

[1.2.0] - 2026-09-18

Added

• A check-own-docs CI job that renders this repository's Markdown and checks the links in it. It is the only job that posts a link-check comment on a pull request, and it posts one only when a link we publish is reported broken. It runs with silent-codes: '0,403,503', so a transient timeout or DNS failure stays quiet and the comment is reserved for a real status such as a 404

Changed

• The action's own steps now run on Node 24: actions/github-script v7 to v9 (three steps) and actions/upload-artifact v4 to v7. Node 20 reached end-of-life on 2026-04-30. None of the action's inputs, outputs or scripts changes. A self-hosted runner needs v2.327.1 or later to run the new pins
• CI moves to actions/checkout v7 and actions/setup-python v7, and a grouped weekly Dependabot config for GitHub Actions is added so that the pins do not fall behind again
• CI serves its own fixtures from 127.0.0.1, so no gating step depends on the public internet any more. A clean page, a followed redirect, a reported error status and that status silenced by silent-codes are all asserted end to end against responses under our control. The scans of good-links.html and broken-links.html remain, as informational smoke that cannot turn CI red
• The fixture scans no longer post a link-check comment on pull requests. Their findings are true by construction, so the comment reported the same fixture on every run and carried no information

Fixed

• The README linked a GitHub Marketplace badge to https://github.com/marketplace/actions/ai-link-checker, which returns 404 — the action was never published there. Found by the new check-own-docs job on its first run

Commits

• 9ba86af Prepare 1.2.0 (#10)
• f7bc244 ci: move GitHub Actions to their Node 24 majors (#9)
• 6f1ed58 Comment only when a link we publish has actually rotted (#8)
• 7103371 Serve CI fixtures from localhost so no gating step is live (#7)
• See full diff 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 sparkly-moxie-de1f0e ready!

Name	Link
🔨 Latest commit	d194182
🔍 Latest deploy log	https://app.netlify.com/projects/sparkly-moxie-de1f0e/deploys/6ab99e398b20e00008fe0134
😎 Deploy Preview	https://deploy-preview-238--sparkly-moxie-de1f0e.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.

[netlify]

✅ Deploy Preview for adorable-cucurucho-69162b ready!

Name	Link
🔨 Latest commit	d194182
🔍 Latest deploy log	https://app.netlify.com/projects/adorable-cucurucho-69162b/deploys/6ab99e3989ed7300081be041
😎 Deploy Preview	https://deploy-preview-238--adorable-cucurucho-69162b.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.