Repository navigation
docs: fix API reference paths and anchors - #1177
Merged
Merged
Conversation
alexbouchardd
approved these changes
Nov 4, 2026
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.
Several documentation links point to API subpages that return 404 or to outdated section anchors. Update links in Event Delivery & Retries, Metrics, Building Your Own UI, and Upgrade to v0.12 to the current single-page API reference and its rendered anchors, including the retry and destination schema links.
The v0.12 upgrade page itself returns HTTP 200; its tenant API link needed correction. These content changes are consumed by the website build.
Validation: checked all 27 API section links on these four pages against live HTML, including each target anchor. The website unit suite also passed all 388 tests; no Outpost runtime code changed.