chore: Update docs changelog - #18898
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
|
| File | Line | Current Link | Should Be |
|---|---|---|---|
includes/docs-changelog.mdx |
24 | /concepts/data-management/data-forwarding/ |
/integrations/data-forwarding/ |
includes/docs-changelog.mdx |
26 | /organization/integrations/data-visualization/amazon-sqs/ |
/integrations/data-forwarding/amazon-sqs/ |
includes/docs-changelog.mdx |
27 | /organization/integrations/data-visualization/ |
/integrations/data-forwarding/ |
includes/docs-changelog.mdx |
28 | /organization/integrations/data-visualization/segment/ |
/integrations/data-forwarding/segment/ |
includes/docs-changelog.mdx |
29 | /organization/integrations/data-visualization/splunk/ |
/integrations/data-forwarding/splunk/ |
Each redirect hop loses ~15% of SEO link equity and adds latency for users.
| ## April 15, 2026 | ||
|
|
||
| ### [docs(agents): Link Cloudflare from product Set Up and Conversations](https://github.com/getsentry/sentry-docs/pull/18884) | ||
| ### [docs(slack): update slack app scopes and format integration docs](https://github.com/getsentry/sentry-docs/pull/17248) | ||
|
|
||
| **Modified:** | ||
| - [Conversations](/product/agents/conversations/) | ||
| - [Set Up](/product/agents/getting-started/) | ||
| - [Slack Integration](https://develop.sentry.dev/integrations/slack/) | ||
|
|
||
| --- | ||
|
|
||
| ### [docs(agents): Document conversation title generation](https://github.com/getsentry/sentry-docs/pull/18878) | ||
| ## April 2, 2026 |
There was a problem hiding this comment.
Bug: The changelog script fetches PRs sorted by updated-desc instead of merge date, causing the generated changelog to display outdated entries instead of the most recently merged ones.
Severity: HIGH
Suggested Fix
Modify the GitHub search query in scripts/update-docs-changelog.mjs. Change the sorting parameter from sort:updated-desc to sort:merged-desc to ensure the script fetches pull requests based on their merge date, not their last update time. This will correctly identify the most recently merged PRs 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 changelog generation script (`scripts/update-docs-changelog.mjs`)
fetches pull requests using `sort:updated-desc`, which sorts by the last update time
rather than the merge time. Although the script later re-sorts the fetched PRs by their
merge date (`merged_at`), the initial fetch may exclude the most recently merged PRs if
they haven't been updated. This results in older, recently-commented-on PRs being
included, leading to a public-facing changelog that displays stale entries instead of
the actual recent documentation updates, misleading users.
Did we get this right? 👍 / 👎 to inform future reviews.
Automated update of the docs changelog from recent merged PRs.