Repository navigation
release(3.2.4): Redis persistence off the request path, lockstep with the agent family - #24
Merged
Merged
Conversation
… the agent family
github-actions
Bot
added
the
documentation
This was referenced Oct 15, 2026
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.
Closes #23
The JVM agent has no bump script, so I moved the version by hand in build.gradle.kts, Version.kt (AGENT_VERSION), the README and the docs (index, installation, release), following the 3.2.3 release commit. The CHANGELOG entry covers the persistence fix merged in #22 plus the two changes that were already under Unreleased (netty pin, runtime engine version detection). The engine pin stays at 4.3.3 and the lockfiles are unchanged because the project version does not appear in them.