fix(java): declare FFE capability from 1.65 - #7456
Merged
Merged
Conversation
Contributor
|
|
leoromanovsky
marked this pull request as ready for review
August 5, 2026 00:59
leoromanovsky
enabled auto-merge (squash)
August 5, 2026 01:00
bm1549
approved these changes
Aug 5, 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
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.
Motivation
dd-trace-java1.65.0 recognizesDD_FEATURE_FLAGS_CONFIGURATION_SOURCE=remote_configand reportsFFE_FLAG_CONFIGURATION_RULESduring the Remote Config capability completeness test. The system-tests capability registry does not currently declare that Java capability, so released-version validation rejects the correctly reported bit as unexpected and fails the Java nightly parametric job. This makes a valid tracer release appear regressed and leaves the nightly pipeline red.Changes
This updates the version-aware Java capability registry so
FFE_FLAG_CONFIGURATION_RULESis expected starting with Java 1.65.0. Earlier Java versions keep their existing expected capability set.Decisions
The capability is declared at
>=1.65.0instead of in the Java base set. Java 1.64.2 contained the registration code, but its feature-flagging subsystem remained disabled under this test configuration because it did not recognize the stable configuration-source setting. Java 1.65.0 recognizes the setting and activates the Remote Config service, which makes the capability observable. This PR stays focused on correcting the released-version contract; it does not change the separate prerelease capability policy.Verification
./format.sh./run.sh TEST_THE_TEST tests/test_the_test/test_capabilities.py— 4 passed