fix(ci): declare cedarpy dependency; repair Scorecard workflow - #291
Merged
Conversation
- cedarpy was never a declared dependency: locally it is present so all tests pass, but CI runners lack it, CedarBackend auto mode fails closed, and the benchmark tests deny every call (main CI red since 2026-06-10). The runtime is not functional without a real Cedar engine. - ossf/scorecard-action@v2 is not a resolvable ref; pinned to the v2.4.3 commit SHA. publish_results disabled while the repo is private (dated note to flip after launch); permissions aligned with the official scorecard template (top-level read-all, job-level writes). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
1 task
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.
Fixes both red workflows on main:
cedarpywas never declared in pyproject. Local environments have it, so the suite passes locally; CI runners do not, soCedarBackendauto mode fails closed and the benchmark tests deny every call (PolicyDeny: benchmark.tool). The runtime is not functional without a real Cedar engine, so it belongs in core dependencies.ossf/scorecard-action@v2is not a resolvable ref (they publish v2.x.y) -- pinned to the v2.4.3 commit SHA.publish_resultsdisabled while the repo is private (it requires a public repo; dated note to flip after the 2026-06-23 launch). Permissions aligned with the official scorecard template.Generated with Claude Code