Skip to content

Fix Dependency Review check: remove conflicting deny-licenses#9

Merged
emmanuelgjr merged 1 commit into
mainfrom
fix/dependency-review-license-config
Jun 14, 2026
Merged

Fix Dependency Review check: remove conflicting deny-licenses#9
emmanuelgjr merged 1 commit into
mainfrom
fix/dependency-review-license-config

Conversation

@emmanuelgjr

Copy link
Copy Markdown
Contributor

Problem

The required Dependency Review check has been failing on every PR (e.g. #8) with:

You cannot specify both allow-licenses and deny-licenses

actions/dependency-review-action@v4 treats allow-licenses and deny-licenses as mutually exclusive and errors out before doing any actual scanning. Because the check is part of the main ruleset, this blocked all merges.

Fix

Remove the deny-licenses block and keep the allow-licenses allowlist.

This preserves the intended policy: with an allowlist, anything not explicitly listed is rejected — which already covers every license the old denylist named (GPL-2.0/3.0, AGPL-*, LGPL-2.0/3.0, SSPL-1.0). The allowlist keeps the permissive set (Apache-2.0, BSD-2/3-Clause, ISC, MIT, MPL-2.0, CC-BY-4.0, CC0-1.0, Unlicense). vulnerability-check and license-check remain enabled.

Effect

Once merged, the Dependency Review check passes on PRs with no disallowed dependency changes, unblocking #8 and future PRs.

…low-licenses)

actions/dependency-review-action rejects specifying both allow-licenses and
deny-licenses ('You cannot specify both...'), so the check errored on every PR.
Keeping the allow-licenses allowlist preserves the policy: anything not listed
(incl. all GPL/AGPL/LGPL/SSPL variants the denylist named) is blocked by default.
@emmanuelgjr emmanuelgjr merged commit bdc7764 into main Jun 14, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant