Skip to content

Fix broken changelog links to non-public PRs#274

Merged
hongyi-chen merged 3 commits into
mainfrom
fix/broken-changelog-pr-links
Jul 1, 2026
Merged

Fix broken changelog links to non-public PRs#274
hongyi-chen merged 3 commits into
mainfrom
fix/broken-changelog-pr-links

Conversation

@hongyi-chen

Copy link
Copy Markdown
Collaborator

Summary

Fixes the only genuinely broken links found in the live docs source while running a broken-link audit.

The 2026.06.17 changelog references PRs #12642 and #12644, but neither exists in the public warpdotdev/warp repository — both return HTTP 404 (they are internal PRs that were not mirrored publicly). This removes the broken hyperlinks while keeping the PR-number references as plain text.

Audit context

A full external-link check was run against src/content/docs (1,194 external links across 338 files). Aside from the two changelog links fixed here, the only other flags were bot-blocking false positives on valid pages, left unchanged:

  • https://platform.openai.com/ — HTTP 403 (Cloudflare bot protection)
  • https://help.openai.com/en/articles/4936856-understanding-tokens — HTTP 403 (bot protection)
  • https://vimdoc.sourceforge.net/htmldoc/insert.html#insert (×2) — times out / 403 to automated requests; page is valid

Note: the warpdotdev/warp LICENSE links in the docs correctly point to master/LICENSE-AGPL (valid); no change needed there.

Root cause

These broken links originate from auto-generated changelog content that references internal PR numbers not present in the public mirror. A durable fix belongs in the changelog generation pipeline so non-public PR references don't emit broken links.


Conversation: https://app.warp.dev/conversation/7c7b3622-41da-4e1e-8caa-22a6c1e94206
Run: https://oz.warp.dev/runs/019f1979-4143-710d-8630-dd3e54168e2d

This PR was generated with Oz.

PRs #12642 and #12644 are referenced in the 2026.06.17 changelog but do
not exist in the public warpdotdev/warp repository (they 404). Remove the
broken hyperlinks while preserving the PR-number references as plain text.

Co-Authored-By: Oz <oz-agent@warp.dev>
@cla-bot cla-bot Bot added the cla-signed label Jun 30, 2026
@vercel

vercel Bot commented Jun 30, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
docs Ready Ready Preview, Comment Jul 1, 2026 9:29pm

Request Review

@hongyi-chen hongyi-chen marked this pull request as ready for review June 30, 2026 18:33
@oz-for-oss

oz-for-oss Bot commented Jun 30, 2026

Copy link
Copy Markdown
Contributor

@hongyi-chen

I'm starting a first review of this pull request.

You can follow along in the session on Warp.

I completed the review and no human review was requested for this pull request.

Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).

Powered by Oz

@hongyi-chen hongyi-chen requested a review from dannyneira June 30, 2026 18:34

@oz-for-oss oz-for-oss Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Overview

This PR removes hyperlinks from two 2026 changelog PR references that point to non-public warpdotdev/warp pull requests, while preserving the release-note text and PR numbers as plain text. The change is narrowly scoped and addresses the broken-link issue without introducing security-sensitive behavior.

Concerns

  • None.

Verdict

Found: 0 critical, 0 important, 0 suggestions

Approve

Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).

Powered by Oz

@hongyi-chen hongyi-chen merged commit 22d6d75 into main Jul 1, 2026
6 of 7 checks passed
@hongyi-chen hongyi-chen deleted the fix/broken-changelog-pr-links branch July 1, 2026 21:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants