-
Notifications
You must be signed in to change notification settings - Fork 107
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] unexpected addition of AND NOASSERTION
to license when updating pywin32-ctypes
#818
Comments
@altendky 👋 I wanted to give you an update. We are looking into the license data and process to understand why you are seeing the |
Similar issue here for another dependency: |
@elrayle do you have any update? We see the same issue for jetty dependencies fetched over maven:
|
Describe the bug
When updating to pypi/pywin32-ctypes@0.2.3 from 0.2.2 the license is identified as
BSD-3-Clause AND NOASSERTION
instead ofBSD-3-Clause
. TheNOASSERTION
is causing an unwanted failure.I have looked at the repo (https://github.com/enthought/pywin32-ctypes/compare/v0.2.2..v0.2.3) and I am unclear what is triggering the new
AND NOASSERTION
. I also looked at the wheels on PyPI and did not identify any seemingly relevant changes around the license metadata or file.To Reproduce
Chia-Network/chia-blockchain#18497
https://github.com/Chia-Network/chia-blockchain/actions/runs/10457582039/job/28957737729?pr=18497#step:3:23
full debug log
workflow source
##[debug]Filtered Changes: [{"change_type":"added","manifest":"poetry.lock","ecosystem":"pip","name":"pywin32-ctypes","version":"0.2.3","package_url":"pkg:pypi/pywin32-ctypes@0.2.3","license":"BSD-3-Clause AND NOASSERTION","source_repository_url":"https://github.com/enthought/pywin32-ctypes","scope":"runtime","vulnerabilities":[]},{"change_type":"removed","manifest":"poetry.lock","ecosystem":"pip","name":"pywin32-ctypes","version":"0.2.2","package_url":"pkg:pypi/pywin32-ctypes@0.2.2","license":"BSD-3-Clause","source_repository_url":"https://github.com/enthought/pywin32-ctypes","scope":"runtime","vulnerabilities":[]}]
Expected behavior
No change to the license is noted and it is accepted.
Screenshots
If applicable, add screenshots to help explain your problem.
Action version
What version of the action are you using in your workflow?
latest v4
The text was updated successfully, but these errors were encountered: