[GSoC 2026] Kafka Streams runner: update the CHANGES.md entry - #39786
Merged
je-ik merged 1 commit intoAug 17, 2026
Merged
Conversation
The entry still described the first skeleton PR — a module whose translation failed fast on every unsupported URN — which has not been true for months. Describes the runner as it is, and says it is opt-in.
je-ik
merged commit Aug 17, 2026
52dadba
into
apache:feat/18479-kafka-streams-runner-skeleton
1 check passed
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.
Part of #18479, for #39785.
The CHANGES.md entry still described the original skeleton —
runners/kafka-streamsas a module whose translation fails fast with an unsupported-URN message until transforms are implemented. That stopped being true months ago. It now describes the runner as it is and says it is opt-in behind-Pwith-kafka-streams-runner.One thing worth deciding separately: the entry sits under the 2.74.0 section, because that is where it was added back in June. On master 2.74.0 is released, so after the merge the entry would sit in a released section rather than in 2.77.0. This branch cannot move it, since it has no 2.77.0 section to move it into — happy to send a follow-up PR to master once the merge lands, or leave it to the master PR, whichever you prefer.