Repository navigation
docs(release): add 2.3.0 release notes - #88
Merged
Merged
Conversation
Convert the [Unreleased] CHANGELOG block to [2.3.0] and fill the gaps: the project website, Event Publisher runtime dependency bumps, the nifi-scripts Poetry resolution fix (#65), release-action SHA pinning (#87) and Werkzeug 3.1.9. Mirror the summary in RELEASE.md with the upgrade note for the MQTT Sink connector setting. Move the website entry out of [2.1.0]: it was merged after v2.2.0 and is in neither the v2.1.0 nor the v2.2.0 tree. Restore the code fences in docs/Event-Publisher.md, which #83 indented far enough to render as literal text. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Luis Alfredo Perez Medina <perezmlal@outlook.com>
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
1 participant
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.
Description
Prepares the v2.3.0 release notes.
[Unreleased]CHANGELOG block to## [2.3.0] - 2026-10-14and adds the entries it was missing: the project website, the Event Publisher runtime dependency bumps (confluent_kafka2.15.1,prometheus_client0.26.0,asn1tools0.169.0), the nifi-scripts Poetry resolution fix (fix(nifi-scripts): repair degraded pip dependency graph #65), the release-action SHA pinning (ci: pin third-party release actions to commit SHAs #87), andWerkzeug3.1.9 (GHSA-g6x2-hccm-hh4m).[2.1.0]. The website was merged after v2.2.0 (feat(website): add React + Vite landing page with GitHub Pages deploy #39) and is in neither the v2.1.0 nor the v2.2.0 tree.Release 2.3.0section toRELEASE.md, with an upgrade note: on an existing stack the new MQTT Sink connector setting only takes effect afterdocker-compose down && docker-compose up --build -d.docs/Event-Publisher.md: chore(agents): adopt the AGENTS.md standard and fix Markdown lint #83 indented two code fences far enough that GitHub renders them as literal text (thepip installblock above them already rendered that way before chore(agents): adopt the AGENTS.md standard and fix Markdown lint #83). The chore(agents): adopt the AGENTS.md standard and fix Markdown lint #83 regression was never in a release, so it has no CHANGELOG entry.Why MINOR (2.3.0): there are no breaking changes. The API, the topic/key conventions and the ASN.1 schemas are unchanged, and
400instead of500is a fix. The release does add backward-compatible functionality: the website, CodeQL, the optionalLOG_VALUE_MAX_LENGTHsetting and pinned image dependencies.Type of change
Notes for reviewers
Docs only; no code or runtime changes. If this merges after 2026-10-14, update the date in the CHANGELOG heading before tagging. After merge, the release is cut by tagging
v2.3.0onmain, which triggers the cosign-signed release workflow.