fix(ci): allow Python-2.0/0BSD in root license check - #1354
Open
saidai-bhuvanesh wants to merge 1 commit into
Open
fix(ci): allow Python-2.0/0BSD in root license check#1354saidai-bhuvanesh wants to merge 1 commit into
saidai-bhuvanesh wants to merge 1 commit into
Conversation
|
@openhands-agent is attempting to deploy a commit to the Nitya Gosain's projects Team on Vercel. A member of the Team first needs to authorize it. |
The 'Check Root Licenses' step's --onlyAllow list was missing Python-2.0 and 0BSD (already present in the frontend/backend/smart-contracts steps), and none of the steps allowed BlueOak-1.0.0. The root dependency tree contains argparse@2.0.1 (Python-2.0) and minimatch@10.2.6 (BlueOak-1.0.0), so the license check failed on every PR. Add Python-2.0, 0BSD and BlueOak-1.0.0 (all permissive/SPDX-recognized) to the root step, and add BlueOak-1.0.0 to the other three steps for consistency. Co-authored-by: openhands <openhands@all-hands.dev>
saidai-bhuvanesh
force-pushed
the
fix/license-check-allow-python2
branch
from
August 15, 2026 06:06
d58b5c0 to
752edb0
Compare
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
2 participants
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.
Aligns the
Check Root Licensesstep's--onlyAllowlist with its sibling steps and adds the permissiveBlueOak-1.0.0.What this fixes (a config inconsistency)
In
.github/workflows/license-check.yml, theCheck Root Licensesstep was missingPython-2.0and0BSDeven though the Frontend/Backend/Smart-Contracts steps already allowed them. The root tree containsargparse@2.0.1(Python-2.0) andminimatch@10.2.6(BlueOak-1.0.0), so the root check failed on every PR. This PR addsPython-2.0;0BSD;BlueOak-1.0.0to the root step andBlueOak-1.0.0to the other steps. All three are permissive, SPDX-recognized licenses.Even after this fix, the Frontend license check still fails:
@img/sharp-libvips-*is a transitive dependency ofsharp. LGPL-3.0-or-later is a copyleft license with source-availability obligations, so allowing it is a project licensing-policy decision only the repo owner can make — I have not added it. Options for the owner:LGPL-3.0-or-laterto the--onlyAllowlists (accepts the LGPL obligations), orsharpdependency, orNote
Other CropChain CI failures (frontend build breakage from duplicated
.catchchains /sourceIndexalready declared) are tracked separately in #1227.