Repository navigation
Use Node 26 for signature parity tooling - #104
Merged
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #104 +/- ##
============================================
+ Coverage 77.04% 78.68% +1.63%
- Complexity 217 220 +3
============================================
Files 13 13
Lines 793 793
Branches 71 71
============================================
+ Hits 611 624 +13
+ Misses 146 134 -12
+ Partials 36 35 -1 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
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.
Java SDK signature parity should exercise the Node 26 reference runtime. Pin CI and the development image to Node 26.12.1, preserving the Java 8/11 CI matrix, the published Java support floor, and the JDK 17 development image.
Add
libatomic1to the JDK image because the Node 26 binary requires it. The first image started withlibatomic.so.1: cannot open shared object file; the rebuilt image starts Node v26.12.1 successfully.Validation: the Docker image builds;
./gradlew --no-daemon checkpasses in a clean archive fixture (89 tests, 3 optional integration skips, no failures). This includes the existing Node CLI signature parity checks. Workflow YAML parsing andgit diff --checkpass. Council review: no issues found. Live API checks remain in normal CI.Validated commit:
2262df3bfc476d47caa5bebf3171f48b20680879.🤖 Claimed by kvz on
framework1/java-sdksince 2026-10-21 · resume:codex resume 01a15ee6-8ad4-7ec2-a0c6-c6d3ac36a367