fix(changelog): Merge bot PR with --admin so updates actually land - #19490
Merged
Merged
Conversation
The weekly changelog workflow regenerates includes/docs-changelog.mdx and opens a bot PR, but merged it with `gh pr merge --auto`. Branch protection on master requires an approving review, which the bot PR never receives, so every run since Aug 17 piled up an unmerged PR and the public changelog stopped updating (last landed Aug 12). Switch to `--admin --delete-branch`, matching bump-api-schema-sha.yml, to bypass the review requirement and required checks (including lint-404, which flags not-yet-deployed links in freshly generated changelog content). The file is fully bot-generated, so admin merge is safe. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![sentry[bot]](https://avatars.githubusercontent.com/in/12637?s=60&v=4){kind=small}
This was referenced Sep 17, 2026
Regenerates includes/docs-changelog.mdx so the Vercel preview shows the up-to-date changelog and merging this PR immediately publishes the ~5 weeks of entries that never landed while the bot PRs were stuck. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
sergical
approved these changes
Sep 18, 2026
Versioned files like configuration/index__v7.x.mdx resolve to <path>__v7.x/, not <path>/index__v7.x/, so the changelog's path-to-URL mapping emitted a broken link that the lint-404 check flags. Skip files containing the __v version indicator; the current version of the page is almost always edited in the same PR and linked separately. Regenerates includes/docs-changelog.mdx accordingly. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
DESCRIBE YOUR PR
The public changelog at docs.sentry.io/changelog stopped updating after Aug 12, 2026. Root cause: the weekly
Update Docs Changelogworkflow still regenerates the file and opens a bot PR correctly, but it merged withgh pr merge --auto. Branch protection onmasterrequires an approving review that the bot PR never receives, so--autositsBLOCKEDforever. Five bot PRs have piled up unmerged since Aug 17 (#19071, #19087, #19186, #19285, #19389).This switches the merge to
--admin --delete-branch, matching the proven pattern inbump-api-schema-sha.yml(whose bot PRs merge fine).--adminto bypass the required review and required checks (includinglint-404, which flags not-yet-deployed doc links in freshly generated changelog content)--delete-branchto avoid stale bot branchesThe 5 stale bot PRs are being closed separately; a fresh
workflow_dispatchrun after this merges will land the backlog.IS YOUR CHANGE URGENT?
Help us prioritize incoming PRs by letting us know when the change needs to go live.
SLA
Thanks in advance for your help!
PRE-MERGE CHECKLIST
Make sure you've checked the following before merging your changes: