Skip to content

docs: fix docs archiving, fail the build on broken anchors, fix account method summaries - #1728

Merged
PhilippeR26 merged 1 commit into
starknet-io:developfrom
PhilippeR26:docs/cleanup
Oct 13, 2026
Merged

PhilippeR26 merged 1 commit into
starknet-io:developfrom
PhilippeR26:docs/cleanup

Conversation

@PhilippeR26

Copy link
Copy Markdown
Collaborator

Motivation and Resolution

Follow-up to the 10.8.0 docs archive. npm run docs:version archived API pages that link to develop instead of the release tag. Since Docusaurus 3, the TypeDoc plugin regenerates the API pages each time Docusaurus loads its plugins, and docs:version loads them without the git revision. The script now passes it, and the manual archiving steps in www/README.md are fixed to match.

Checking the docs build showed two more problems: broken anchors never failed the build, and 9 account methods showed the description of another method in the API docs.

RPC version (if applicable)

N/A

Usage related changes

  • API docs: 9 AccountInterface / Account methods (estimateAccountDeployFee, declare, deploy...) now show their own summary, @returns and @remarks. @inheritdoc tags replaced them with the text of another method (estimateInvokeFee, execute...). No code change.

Development related changes

  • npm run docs:version passes GIT_REVISION_OVERRIDE. The [Manual] Documentation Version PR workflow calls this script, so it is fixed too.
  • www/README.md: manual archiving steps fixed (empty www/docs/API but keep .gitkeep, pass the revision in every command, build after the archive step as a link check, add the banner step).
  • www/docusaurus.config.ts: onBrokenAnchors: 'throw' (a full build finds no broken anchor today), and DOCS_ONLY_CURRENT removed (no use left).

Checklist:

  • Performed a self-review of the code
  • Rebased to the last commit of the target branch (or merged it into my branch)
  • Documented the changes in code (API docs will be generated automatically)
  • Updated the tests
  • All tests are passing

…nt method summaries

`npm run docs:version` now passes `GIT_REVISION_OVERRIDE` to Docusaurus. Since the move to Docusaurus 3, docusaurus-plugin-typedoc 1.x generates the API pages each time Docusaurus loads its plugins, and `docs:version` loads them. So the archived API pages linked to `develop` instead of the release tag. The old 0.21 plugin generated them only during a build, so the 7.6.4, 8.6.0 and 9.2.1 archives were not affected.

Fix the manual archiving steps in `www/README.md`. First empty `www/docs/API` but keep its `.gitkeep`: TypeDoc does not empty this folder, so old pages would end up in the archive. Pass the git revision in the two commands that missed it. Run the build after the archive step, as a link check. Add the step that gives the new version its `banner` entry.

Remove `DOCS_ONLY_CURRENT` from `www/docusaurus.config.ts`. It only helped to generate the API pages before an archive, and `docs:version` now does this by itself.

Set `onBrokenAnchors` to `throw`. Docusaurus 3 only warns by default. A full build finds no broken anchor in any version today.

Remove the 10 `@inheritdoc` tags from `src/account/interface.ts`. TypeDoc replaced the summary, `@returns` and `@remarks` of 9 methods with the ones of the referenced method, so the API docs described `estimateAccountDeployFee` as an INVOKE fee estimate. Each comment already has its own text.
@PhilippeR26
PhilippeR26 merged commit f74ab1f into starknet-io:develop Oct 13, 2026
9 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

🎉 This PR is included in version 11.3.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant