Skip to content

chore: Update docs changelog - #18918

Open
getsantry[bot] wants to merge 1 commit into
masterfrom
bot/update-docs-changelog-20260803
Open

chore: Update docs changelog#18918
getsantry[bot] wants to merge 1 commit into
masterfrom
bot/update-docs-changelog-20260803

Conversation

@getsantry

@getsantry getsantry Bot commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

Automated update of the docs changelog from recent merged PRs.

@vercel

vercel Bot commented Aug 3, 2026

Copy link
Copy Markdown

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

Project Deployment Actions Updated (UTC)
sentry-docs Ready Ready Preview Aug 3, 2026 12:35am
1 Skipped Deployment
Project Deployment Actions Updated (UTC)
develop-docs Ignored Ignored Preview Aug 3, 2026 12:35am

Request Review

@getsantry
getsantry Bot enabled auto-merge (squash) August 3, 2026 00:25
@github-actions

github-actions Bot commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

⚠️ Redirect Chain Issues Detected

This PR introduces or contains redirect chains that degrade SEO and add latency.

Content Links Pointing to Redirects (5 found)

These links point to URLs that redirect. Update them to point directly to the final destination:

File Line Current Link Should Be
includes/docs-changelog.mdx 128 /concepts/data-management/data-forwarding/ /integrations/data-forwarding/
includes/docs-changelog.mdx 130 /organization/integrations/data-visualization/amazon-sqs/ /integrations/data-forwarding/amazon-sqs/
includes/docs-changelog.mdx 131 /organization/integrations/data-visualization/ /integrations/data-forwarding/
includes/docs-changelog.mdx 132 /organization/integrations/data-visualization/segment/ /integrations/data-forwarding/segment/
includes/docs-changelog.mdx 133 /organization/integrations/data-visualization/splunk/ /integrations/data-forwarding/splunk/

Each redirect hop loses ~15% of SEO link equity and adds latency for users.

Comment on lines +1 to +10
## July 31, 2026

### [docs(agents): Link Cloudflare from product Set Up and Conversations](https://github.com/getsentry/sentry-docs/pull/18884)
### [docs(product): Update screenshots on Ownership Rules page](https://github.com/getsentry/sentry-docs/pull/18882)

**Modified:**
- [Conversations](/product/agents/conversations/)
- [Set Up](/product/agents/getting-started/)
- [Ownership Rules](/product/issues/ownership-rules/)

---

### [docs(agents): Document conversation title generation](https://github.com/getsentry/sentry-docs/pull/18878)
### [docs(product): Update stale image on Censecutive HTTP Performance issue page](https://github.com/getsentry/sentry-docs/pull/18808)

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.

Bug: The changelog script fetches PRs by update time but sorts by merge time, causing recently merged PRs to be incorrectly omitted from the output.
Severity: MEDIUM

Suggested Fix

Modify the GitHub API query to fetch pull requests sorted by merge date instead of update date. Change the query parameter from sort:updated-desc to sort:merged-desc. This will align the initial fetch criteria with the final sorting logic, ensuring the most recently merged PRs are always considered for the changelog.

Prompt for AI Agent
Review the code at the location below. A potential bug has been identified by an AI
agent. Verify if this is a real issue. If it is, propose a fix; if not, explain why it's
not valid.

Location: includes/docs-changelog.mdx#L1-L10

Potential issue: The script responsible for generating the changelog fetches the 50 most
recently updated pull requests (`sort:updated-desc`), but then sorts them by their merge
date (`merged_at`) before selecting the top 20 for inclusion. This logical mismatch
allows old pull requests that receive a recent update (e.g., a new comment) to enter the
initial candidate pool. Consequently, these older but recently-updated PRs can displace
genuinely recent, but less recently-updated, merged PRs from the final changelog. This
results in an incomplete and inaccurate changelog that omits some of the latest changes.

Did we get this right? 👍 / 👎 to inform future reviews.

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.

0 participants