Summary
Sixteen current default-branch documentation checks complete Documenter's check/render pipeline and then fail only while publishing gh-pages. Eleven repositories fail SSH authentication with Permission denied (publickey); five fail HTTPS pushes with HTTP 403.
These are repository credential/permission failures, not documentation build failures. Changing package source or weakening Documenter checks would not fix them.
SSH deploy-key failures
The jobs below reach CheckDocument/RenderDocument, enter deploydocs, and fail while fetching or pushing the SSH remote:
For these repositories, rotate/re-register the DOCUMENTER_KEY pair and ensure the public deploy key has write access. CatalystNetworkAnalysis.jl already has the repository-specific diagnosis at SciML/CatalystNetworkAnalysis.jl#75.
HTTPS token-permission failures
These jobs also build and render successfully, then git push ... HEAD:gh-pages receives HTTP 403:
For these repositories, grant Actions GITHUB_TOKEN write access to repository contents, or configure a valid Documenter deploy key consistently with the rest of the organization.
After correcting the repository settings, rerun the linked workflow runs to verify publication and clear the red default-branch checks.
Investigated by an AI agent using Codex CLI 0.151.0 (model: gpt-5.6-sol; session: local session ID 01a0598f-11b9-72d1-91d9-b2fbb186557d).
Summary
Sixteen current default-branch documentation checks complete Documenter's check/render pipeline and then fail only while publishing
gh-pages. Eleven repositories fail SSH authentication withPermission denied (publickey); five fail HTTPS pushes with HTTP 403.These are repository credential/permission failures, not documentation build failures. Changing package source or weakening Documenter checks would not fix them.
SSH deploy-key failures
The jobs below reach
CheckDocument/RenderDocument, enterdeploydocs, and fail while fetching or pushing the SSH remote:For these repositories, rotate/re-register the
DOCUMENTER_KEYpair and ensure the public deploy key has write access. CatalystNetworkAnalysis.jl already has the repository-specific diagnosis at SciML/CatalystNetworkAnalysis.jl#75.HTTPS token-permission failures
These jobs also build and render successfully, then
git push ... HEAD:gh-pagesreceives HTTP 403:For these repositories, grant Actions
GITHUB_TOKENwrite access to repository contents, or configure a valid Documenter deploy key consistently with the rest of the organization.After correcting the repository settings, rerun the linked workflow runs to verify publication and clear the red default-branch checks.
Investigated by an AI agent using Codex CLI 0.151.0 (model: gpt-5.6-sol; session: local session ID
01a0598f-11b9-72d1-91d9-b2fbb186557d).