fix(web): publish current docs at root routes#1627
Merged
Conversation
Deploying agentv with
|
| Latest commit: |
db90ffe
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://c459004d.agentv.pages.dev |
| Branch Preview URL: | https://docs-route-banner.agentv.pages.dev |
christso
force-pushed
the
docs-route-banner
branch
from
b773757 to
db90ffe
Compare
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
1 participant
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.
Summary
Current public docs now render directly at root
/docs/...URLs instead of sending users through the archivedv4.42.4tree. The reported/docs/v4.42.4/targets/llm-providers/URL is generated as a real archived page again, and/docs/next/...remains available as a compatibility redirect to the root docs path.The visible docs version selector now labels the root docs as
Currentinstead ofNext, avoiding canary-style wording for the public docs experience.Validation
bun --filter @agentv/web buildemitted archived LLM provider content under/docs/v4424/targets/llm-providers/while root docs redirected to/docs/v4.42.4/.bun --filter @agentv/web buildbun --filter @agentv/web check:routescurlagainst local preview returned 200 for/docs/,/docs/targets/llm-providers/, and/docs/v4.42.4/targets/llm-providers/.agent-browser --session docs-route-banner open http://127.0.0.1:4322/docs/agent-browser --session docs-route-banner open http://127.0.0.1:4322/docs/v4.42.4/targets/llm-providers/Dedicated CE code review was skipped because this harness only permits spawning sub-agents when the user explicitly requests delegation. I ran a manual diff review instead and tightened the redirect map/checker to use MDX slugs and validate every archived manifest route.
Post-Deploy Monitoring & Validation
No additional operational monitoring required: this is a static docs routing/content build change with no runtime service, database, or API behavior. After deploy, validate with HTTP 200 checks for
/docs/,/docs/targets/llm-providers/, and/docs/v4.42.4/targets/llm-providers/; rollback trigger is any 404 or unexpected redirect loop on those paths.Related
Related: Bead av-1q3t