(SPEED-2066): skip release steps on pull requests - #59
Merged
Conversation
pamellix
force-pushed
the
dependabot-release-guard
branch
from
August 5, 2026 06:47
34a9656 to
5938204
Compare
pamellix
changed the title
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.
Summary:
Root cause:
Dependabot pull requests have no release secrets, while trusted pull requests currently attempt canary publication. Both paths fail after validation even though npm ci, formatting, and tests pass. Publishing belongs to the existing push-to-main release path.
Validation: