Skip to content

docs: sync api reference 2026-08-03 - #102

Open
JamesLawton wants to merge 2 commits into
mainfrom
docs/update-api-reference-2026-08-03
Open

docs: sync api reference 2026-08-03#102
JamesLawton wants to merge 2 commits into
mainfrom
docs/update-api-reference-2026-08-03

Conversation

@JamesLawton

Copy link
Copy Markdown
Collaborator

What changed

  • api-reference/trails-api.gen.yaml — add EVERLONG to the RouteProvider enum; bump the RIDL schema hash in the header comment to match the release-branch source.
  • api-reference/trails-api.gen.json — add EVERLONG to the same enum (kept alphabetized between CCTP and GASZIP).
  • api-reference/before-annotations-trails-api.gen.json — same enum update in the pre-annotation snapshot.

No endpoint pages needed to be added or removed. The only substantive spec drift against trails-api release in the last 7 days is the new EVERLONG provider value.

Source of truth

  • 0xsequence/trails-api#1023 — "Everlong hotfix" cherry-picking #1015 (Add everlong provider) into release, merged 2026-07-28.
  • proto/trails-types.ridl on release (RouteProvider enum) — EVERLONG listed between CCTP and GASZIP.
  • proto/docs/trails-api.gen.yaml on release (schema hash 6cf9188c5e4b19ba31646a1448e66daf4691a6af).

Verification

diff /home/user/trails-api/proto/docs/trails-api.gen.yaml \
     /home/user/trails-docs/api-reference/trails-api.gen.yaml

after this PR should show only the webrpc-gen version header and the docs-only servers: block (both intentional local overrides), with no enum/schema differences.

Generated by the Trails Docs weekly agent.


Generated by Claude Code

Sync OpenAPI spec from trails-api release branch to add the EVERLONG
value to the RouteProvider enum (introduced in 0xsequence/trails-api#1023).

Generated by the Trails Docs weekly agent.
@mintlify

mintlify Bot commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
trails 🔴 Failed Aug 3, 2026, 9:26 AM

💡 Tip: Enable Workflows to automatically generate PRs for you.

The previous preview build failed with a generic "unknown error occurred"
from Mintlify (deployment reached "Updating all paths..." after
successfully validating the config and OpenAPI files). The sibling PR
#103 opened seconds later against the same base built cleanly, so this
is a transient Mintlify-side hiccup rather than a diff-side issue —
retrigger by pushing an empty commit.
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.

1 participant