chore: Update docs changelog - #19285
Closed
getsantry[bot] wants to merge 1 commit into
Closed
getsantry[bot] wants to merge 1 commit into
getsantry[bot] wants to merge 1 commit into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
github-actions
Bot
added
the
Priority: Needs Triage
Contributor
|
Please update the IS YOUR CHANGE URGENT? section of the PR description:
This information helps the Docs team prioritize your review. |
6 tasks
Contributor
|
Closing this stale auto-generated changelog PR. These piled up because the workflow used |
auto-merge was automatically disabled
September 17, 2026 21:47
Pull request was closed
coolguyzone
added a commit
that referenced
this pull request
Sep 18, 2026
…19490) ## DESCRIBE YOUR PR The public changelog at docs.sentry.io/changelog stopped updating after **Aug 12, 2026**. Root cause: the weekly `Update Docs Changelog` workflow still regenerates the file and opens a bot PR correctly, but it merged with `gh pr merge --auto`. Branch protection on `master` requires an approving review that the bot PR never receives, so `--auto` sits `BLOCKED` forever. 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 in `bump-api-schema-sha.yml` (whose bot PRs merge fine). - Use `--admin` to bypass the required review and required checks (including `lint-404`, which flags not-yet-deployed doc links in freshly generated changelog content) - Add `--delete-branch` to avoid stale bot branches - The generated file is fully bot-authored, so admin merge is safe The 5 stale bot PRs are being closed separately; a fresh `workflow_dispatch` run 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. - [ ] Urgent deadline (GA date, etc.): <!-- ENTER DATE HERE --> - [ ] Other deadline: <!-- ENTER DATE HERE --> - [x] None: Not urgent, can wait up to 1 week+ ## SLA - Teamwork makes the dream work, so please add a reviewer to your PRs. - Please give the docs team up to 1 week to review your PR unless you've added an urgent due date to it. Thanks in advance for your help! ## PRE-MERGE CHECKLIST *Make sure you've checked the following before merging your changes:* - [ ] Checked Vercel preview for correctness, including links - [ ] PR was reviewed and approved by any necessary SMEs (subject matter experts) - [ ] PR was reviewed and approved by a member of the [Sentry docs team](https://github.com/orgs/getsentry/teams/docs) --------- 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
1 participant
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.
Automated update of the docs changelog from recent merged PRs.