[FLINK-40090][docs] Modernize cryptography export notice in distribution README#28677
Open
MartijnVisser wants to merge 2 commits into
Open
[FLINK-40090][docs] Modernize cryptography export notice in distribution README#28677MartijnVisser wants to merge 2 commits into
MartijnVisser wants to merge 2 commits into
Conversation
f126ffb to
039d258
Compare
The Flink CLI e2e test feeds the shipped flink-dist README.txt to the WordCount example and asserts a fixed output row count. Rewriting the export notice changed the token count from 192 to 236. Generated-by: Claude Opus 4.8
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.
What is the purpose of the change
Adhering to the requirements outlined in https://infra.apache.org/crypto.html#inform
Brief change log
Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:
@Public(Evolving): noDocumentation
Was generative AI tooling used to co-author this PR?