Override confluent-kafka license #19100
Merged
+2
−0
Conversation
This file contains 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
Kyle-Neale
changed the base branch from
kyle.neale/update-confluent-kafka
to
master
Kyle-Neale
changed the base branch from
master
to
kyle.neale/update-confluent-kafka
Kyle-Neale
merged commit 4639a28
into
kyle.neale/update-confluent-kafka
21 checks passed
Kyle-Neale
added a commit
that referenced
this pull request
Nov 21, 2024
* Bump confluent-kafka to 2.6.1 to address CVE * Add changelog * Override confluent-kafka license (#19100)
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.
What does this PR do?
License metadata is wrong in latest release: https://pypi.org/project/confluent-kafka/2.6.1/. They still use the Apache 2.0 license so we just hardcode it here to compensate.
Motivation
Review checklist (to be filled by reviewers)
qa/skip-qalabel if the PR doesn't need to be tested during QA.backport/<branch-name>label to the PR and it will automatically open a backport PR once this one is merged