fix: trigger scorecard on default branch events, not releases#624
Merged
Conversation
The OSSF Scorecard action only supports the repository default branch. Triggering on release (created) runs against the tag ref (e.g. 2.3.0-rc.1) and fails with 'only default branch is supported', breaking every RC/release. Switch to the OSSF-recommended triggers: push to main, a weekly schedule, and branch_protection_rule changes.
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.
Problem
The Scorecard supply-chain workflow runs
on: release: [created]. The OSSF Scorecard action only supports the repository's default branch — a release event checks out the tag ref (e.g.2.3.0-rc.1), so the action aborts:This means the scorecard job fails on every RC/release. See run: https://github.com/authorizerdev/authorizer/actions/runs/26877785127/job/79269599505
Fix
Replace the
releasetrigger with the OSSF-recommended events:pushtomain— re-score on every merge to the default branchschedule— weekly cron (Mon 07:20 UTC) so the published score stays freshbranch_protection_rule— re-score when branch protection changes (a scored check)No change to permissions, publishing, or the action version.