Symptom
The "Publish docs to Wiki" workflow has failed on every docs push in its visible history — at least six consecutive runs back to 2026-08-12 (latest):
fatal: could not read Password for 'https://***@github.com': No such device or address
##[error]Process completed with exit code 128.
secrets.WIKI_ACTION_TOKEN is resolving empty (or the PAT behind it has expired), so the authenticated URL degrades to a password prompt no runner can answer.
Impact
The GitHub wiki mirror of docs/ is frozen at whatever it held before the token died. Everything merged to docs since then exists on main and Read the Docs but not on the wiki, including at minimum: the FoxESS A-series supported-devices entry (#2073) and its follow-up amendments, the Autel MaxiCharger entry (#2072), and the multiple-central-systems documentation (#2078). Anyone reading the wiki is reading stale docs.
Fix — maintainer-only
No PR can fix this: the WIKI_ACTION_TOKEN secret needs to be rotated (wiki pushes require a token with classic repo scope, or equivalent fine-grained access; the default GITHUB_TOKEN cannot push to the wiki repo, which is presumably why the secret exists). After rotating, re-running the most recent failed run — or any push touching docs/ — resyncs the mirror, since the workflow rsyncs the whole tree with --delete.
Filing this as an issue rather than a PR precisely because only a repo admin can act on it.
Symptom
The "Publish docs to Wiki" workflow has failed on every docs push in its visible history — at least six consecutive runs back to 2026-08-12 (latest):
secrets.WIKI_ACTION_TOKENis resolving empty (or the PAT behind it has expired), so the authenticated URL degrades to a password prompt no runner can answer.Impact
The GitHub wiki mirror of
docs/is frozen at whatever it held before the token died. Everything merged to docs since then exists on main and Read the Docs but not on the wiki, including at minimum: the FoxESS A-series supported-devices entry (#2073) and its follow-up amendments, the Autel MaxiCharger entry (#2072), and the multiple-central-systems documentation (#2078). Anyone reading the wiki is reading stale docs.Fix — maintainer-only
No PR can fix this: the
WIKI_ACTION_TOKENsecret needs to be rotated (wiki pushes require a token with classicreposcope, or equivalent fine-grained access; the defaultGITHUB_TOKENcannot push to the wiki repo, which is presumably why the secret exists). After rotating, re-running the most recent failed run — or any push touchingdocs/— resyncs the mirror, since the workflow rsyncs the whole tree with--delete.Filing this as an issue rather than a PR precisely because only a repo admin can act on it.