chore: skip typing_extensions license check#9120
Merged
Conversation
julian-risch
approved these changes
Mar 27, 2025
Collaborator
Pull Request Test Coverage Report for Build 14105778459Details
💛 - Coveralls |
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.
Related Issues
failing license compliance workflow: https://github.com/deepset-ai/haystack/actions/runs/14095817546/job/39482814951
this happens because
typing-extensions==4.13.0was released yesterday with Python Software Foundation License 2.0 and the GitHub action that checks licenses does not recognize it (see Support PSF license(s) pilosus/pip-license-checker#143)(similar PR in core-integrations: chore: skip
typing_extensionslicense check haystack-core-integrations#1567)Proposed Changes:
typing_extensionsto excluded packagesHow did you test it?
Tested locally using the docker image:
Checklist
fix:,feat:,build:,chore:,ci:,docs:,style:,refactor:,perf:,test:and added!in case the PR includes breaking changes.