Skip to content

revert(docs): roll back PR #902#906

Merged
DeveloperAlly merged 2 commits into
docs-v2from
revert/pr-902
May 22, 2026
Merged

revert(docs): roll back PR #902#906
DeveloperAlly merged 2 commits into
docs-v2from
revert/pr-902

Conversation

@DeveloperAlly
Copy link
Copy Markdown
Collaborator

Summary

Reverts PR #902 (c918866e9, Handover/docs v2 into docs v2 dev 20260518 (#902)) from docs-v2 because it caused missing docs pages and multiple 404s in production.

This branch is based on current origin/docs-v2 and preserves the post-#902 changelog/sitemap updates already on the branch:

Revert Notes

  • Reverted the PR Handover/docs v2 into docs v2 dev 20260518 #902 squash merge in a dedicated worktree on revert/pr-902.
  • Resolved the three revert conflicts by keeping current docs-v2 versions of:
    • sitemap-ai.xml
    • snippets/composables/pages/changelogs/protocol/go-livepeer.mdx
    • v2/resources/changelog/protocol/go-livepeer.mdx
  • Kept the current Resource HUB redirect invariant required by repo navigation validation:
    • v2/resources/redirect
    • /v2/resources/redirect -> /v2/resources/portal
  • Avoided reintroducing literal merge-conflict markers from older restored files by preserving the pre-revert versions of those marker-bearing files.
  • Removed the invalid restored jsconfig.json, which made Mintlify parse a non-config route tree as YAML.

Validation

Passed:

  • Pre-commit hard gates on the revert commit
  • node operations/tests/unit/docs-navigation.test.js --strict-missing
    • Result: passed with warnings only for existing unrepresented canonical files
  • Changed-file conflict marker check
    • Result: no changed files contain conflict marker starts
  • Branch freshness check
    • Result: branch contains current origin/docs-v2

Known validation issue:

  • npx mintlify@4.2.459 validate fails with:
    • error end of the stream or a document separator is expected (215:16)
  • I verified the same Mintlify error occurs after temporarily restoring the pre-revert HEAD~1 docs.json and scoped navigation files, so this parse failure is not introduced by this rollback.

Risk

This is a large rollback because PR #902 was a large squash merge. The PR intentionally prioritizes restoring the pre-#902 docs-v2 content surface while preserving post-merge changelog/sitemap updates and current navigation invariants needed for validation.

This reverts commit c918866.

allow-deletions: true

# Conflicts:
#	sitemap-ai.xml
#	snippets/composables/pages/changelogs/protocol/go-livepeer.mdx
#	v2/resources/changelog/protocol/go-livepeer.mdx
@DeveloperAlly DeveloperAlly added type: bug Something isn't working Docs Created by Linear-GitHub Sync Docs:v2 v2 of Documentation Label docs-v2 Livepeer docs v2 issue scope labels May 22, 2026
@mintlify
Copy link
Copy Markdown

mintlify Bot commented May 22, 2026

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

Project Status Preview Updated (UTC)
na-36 🟢 Ready View Preview May 22, 2026, 1:42 AM

@github-actions
Copy link
Copy Markdown
Contributor

📊 V2 Browser Sweep Results

❌ Test report not found. The test may have failed before report generation.

  • Likely failed in setup/cache/server-start steps before npm run test:v2-pages.

Standardised frontmatter scalars to double quotes and replaced em-dash
characters with en-dash in authored MDX. Generated by
.github/workflows/remediator-brand-repair-frontmatter-and-em-dashes.yml
@DeveloperAlly DeveloperAlly merged commit 08735a3 into docs-v2 May 22, 2026
1 check passed
@DeveloperAlly DeveloperAlly deleted the revert/pr-902 branch May 22, 2026 03:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Docs:v2 v2 of Documentation Label Docs Created by Linear-GitHub Sync docs-v2 Livepeer docs v2 issue scope type: bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant