fix(ci): restrict dev releases to commits on main#94
Merged
Takaros999 merged 1 commit intomainfrom Feb 16, 2026
Merged
Conversation
Prevent publishing dev preview releases from unmerged code by adding two layers of protection to all publish workflows: a job-level branch guard that requires workflow_dispatch to run from main, and a git ancestry check that validates the target commit is reachable from origin/main. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Gr1dlock
approved these changes
Feb 16, 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
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
Previously, anyone with write access could trigger a dev release from any branch or provide a commit SHA from unmerged code. Even though these are dev previews, publishing unreviewed code is a supply chain risk.
This adds two layers of protection to all 4 publish workflows: a job-level guard that restricts
workflow_dispatchto themainbranch, and agit merge-base --is-ancestorcheck that validates the target commit actually exists on main.Part of DEV-2676