Skip to content

Mark deprecated API operations with deprecated: true - #17

Open
BPKelley wants to merge 1 commit into
mainfrom
bkelley/doc-569-deprecated-operations
Open

Mark deprecated API operations with deprecated: true#17
BPKelley wants to merge 1 commit into
mainfrom
bkelley/doc-569-deprecated-operations

Conversation

@BPKelley

Copy link
Copy Markdown

Summary

  • Adds deprecated: true to all 120 deprecated API operations in ngrok.yaml
  • Covers: Bot Users, all 5 Backend types (Failover, HTTP Response, Static, Tunnel Group, Weighted), Edges HTTPS/TCP/TLS (CRUD + all route modules), and Tunnels
  • Mintlify natively renders deprecation indicators from this OpenAPI field, both in the nav sidebar and on individual pages

Context

DOC-569: Deprecated API endpoints have no deprecation signal in page content — only the sidebar grouping, which AI agents and LLMs can't see. This causes tools like Claude to repeatedly suggest deprecated APIs.

Companion PR: ngrok/ngrok-docs#2070 (adds <Warning> callouts in MDX — belt-and-suspenders approach while we confirm the OpenAPI approach renders well enough on its own).

Test plan

  • Point ngrok-docs/docs.json openapi field at local ngrok.yaml, run pnpm run dev, and verify deprecated pages (e.g. /docs/api-reference/botusers/create) show Mintlify's native deprecated label
  • Verify non-deprecated pages (e.g. /docs/api-reference/apikeys/list) are unaffected
  • Validate YAML with python3 -c "import yaml; yaml.safe_load(open('ngrok.yaml'))"

🤖 Generated with Claude Code

Adds the OpenAPI `deprecated: true` field to all deprecated operations
(Bot Users, Backends, Edges, Tunnels) so that Mintlify and other
consumers can render deprecation indicators natively.

Companion to ngrok/ngrok-docs#2070.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@BPKelley
BPKelley marked this pull request as draft May 18, 2026 22:42
@BPKelley
BPKelley marked this pull request as ready for review July 20, 2026 18:14
@BPKelley

Copy link
Copy Markdown
Author

@copilot can you sync this PR with Main (pull the latest changes, since this PR is very stale) and let us know if anything has conflicts? Then if not, please run a code review.

Copilot AI commented Jul 20, 2026

Copy link
Copy Markdown

@copilot can you sync this PR with Main (pull the latest changes, since this PR is very stale) and let us know if anything has conflicts? Then if not, please run a code review.

Synced check complete on 8f302b4: this branch is already up to date with origin/main (git merge origin/main reported “Already up to date”), so there were no conflicts. I also ran a code review on the PR diff and found no actionable issues.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants