Pin docusaurusVersion to V1 so the website deploy works again - #1624
Merged
Conversation
The website publish has failed since sbt-mdoc was bumped from 2.4.0 to
2.9.0 in April, with:
error Command "deploy" not found.
2.4.0 hardcoded `USE_SSH=true yarn publish-gh-pages`. 2.9.0 introduced a
docusaurusVersion setting that defaults to V3, whose publish step runs
`yarn deploy` instead. website/ is still Docusaurus 1 -- siteConfig.js,
sidebars.json, no docusaurus.config.js -- and its package.json defines
publish-gh-pages, not deploy.
Declaring V1 restores `USE_SSH=true yarn publish-gh-pages`, matching what
2.4.0 ran. The deploy key was never the problem; ssh authenticated fine
in the failing runs.
Verified by building the site end to end with docs/docusaurusCreateSite:
mdoc, yarn install and the Docusaurus 1 build all succeed, producing 248
html files.
Migrating the site to Docusaurus 3 is the longer-term fix and is left
alone here.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QRbVCYWp3bquNaXPYW12JY
julien-truffaut
force-pushed
the
fix-docs-deploy
branch
from
September 4, 2026 14:11
9d4a340 to
4c2d455
Compare
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.
The website has not been republished since April. The publish step of every release run fails with:
Most recently in the 3.4.0-RC2 release run, so the site still documents 3.3.0.
Cause
Scala Steward bumped sbt-mdoc 2.4.0 → 2.9.0 in 7e80437 (2026-04-14).
2.4.0 hardcoded the Docusaurus 1 command:
2.9.x introduced a
docusaurusVersionsetting and defaults it toV3:But
website/is still Docusaurus 1 —siteConfig.js,sidebars.json,pages/, nodocusaurus.config.js— and itspackage.jsondefinespublish-gh-pages, with nodeployscript. Hence the error.Declaring
V1restoresUSE_SSH=true yarn publish-gh-pages, exactly what 2.4.0 ran.Not the deploy key
Worth stating since the error message names
install_ssh.sh:GIT_DEPLOY_KEYis fine. The failing runs show ssh authenticating normally before the script gets to the yarn command:Verification
docs/docusaurusCreateSite— the non-publishing counterpart of the failing task — runs mdoc,yarn installand the Docusaurus 1 build end to end, producing 248 html files.Note
yarn installneeds Node ≥ 20.18.1 (cheerio@1.2.0); the CI runner satisfies this, and itsyarn installalready succeeded in the failing runs — only the command after it failed.Follow-up
Docusaurus 1 has been end-of-life for years. Migrating
website/to Docusaurus 3 and dropping this setting is the real fix; this restores publishing in the meantime.🤖 Generated with Claude Code
https://claude.ai/code/session_01QRbVCYWp3bquNaXPYW12JY