Skip to content

docs: fix dead release/2.0 links - #265

Open
leoafarias wants to merge 1 commit into
mainfrom
fix/docs-dead-release-links
Open

leoafarias wants to merge 1 commit into
mainfrom
fix/docs-dead-release-links

Conversation

@leoafarias

@leoafarias leoafarias commented Nov 20, 2026 •

Copy link
Copy Markdown
Collaborator

Requested by Leo · project thread

Point the schema converter guide’s contribution and publishing links at main. No other blob/release/2.0 or tree/release/2.0 links remain under docs/.

Validation: npx --yes @docs.page/cli@2.0.0 check passed locally.


Open workspace in Conductor

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 20, 2026 •

Copy link
Copy Markdown
Codex Review Summary: ✅ Completed

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-11-20T22:27:08.496533Z 6796efb PR opened
🔒 Security Review ✅ Completed 2026-11-20T22:27:35.140052Z 6796efb PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@leoafarias leoafarias self-assigned this Nov 20, 2026

@leoafarias leoafarias left a comment

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

VERDICT: MERGE

  1. No blocking findings. Both replacement links in the schema converter guide resolve on main, and a scan of the tracked PR tree found no links to the deleted release/2.0 branch. PUBLISHING.md still mentions that ref in a release command example, not in a link; the runbook also describes the main alternative.
  2. Documentation / validate passed on 6796efb and reported no documentation issues. CI package tests and the API compatibility check also passed. The diff only changes two link destinations, follows the repository's contribution conventions, and introduces no API changes or behavior requiring new tests.
  3. PR #264's Documentation log reports failures on these same two links. Merge #265 first, then update #264 from main and confirm Documentation passes before merging it.

This branch has not been deployed

No deployments
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