Repository navigation
ci(ddl-changes): Bump getsentry/action-migrations to v1.4.1 - #8568
Merged
Merged
Conversation
Co-Authored-By: Elio Di Nino <[email protected]>
ElioDiNino
approved these changes
Oct 19, 2026
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.
Bumps
getsentry/action-migrationsfrom v1.2.2 to v1.4.1. This replaces the Dependabot PR #8558 for v1.4.0, which is now closed.v1.3.0 and v1.4.0 posted a comment with only the header on every PR, even when
cmdreturned nothing. That hits Snuba on every PR, becauseddl-changes.ymlalways passes./snuba/migrations/groups.pyand relies on empty output to keep quiet. v1.4.1 (getsentry/action-migrations#37) goes back to posting nothing when no migration produces SQL. It also deletes its earlier comment if a later push removes the migration.This PR doesn't include the Dependabot skip from #8558. On a PR with no SQL, v1.4.1 only lists comments, and there's nothing to delete, so a read-only token works.
The SHA is pinned to the commit tagged
v1.4.1. v1.4.0 also changed how comments sync: the action now keeps one SQL comment pernameand replaces old ones instead of adding duplicates.via Elio Di Nino.
--
View Junior Session [Sentry]