Update data#472
Conversation
Greptile SummaryAutomated data update adding JetBrains JBR
Confidence Score: 4/5Safe to merge with one data-consistency question: verify whether the musl JDK b508.4 omission in ga/linux/x86_64.json is intentional. Most of the changes are straightforward build-catalog additions with consistent checksums and correct metadata. The EA corrections fix a previously malformed version string and timestamp. The one concern is that ga/linux/x86_64.json receives a new musl JRE for b508.4 but not the corresponding musl JDK, while alpine-linux/x86_64.json gets both — leaving the two endpoints out of sync for that build type. public/api/jvm/ga/linux/x86_64.json — check whether the musl JDK b508.4 entry should be present here in addition to the musl JRE b508.4 that was added. Important Files Changed
|
| "version": "28.0.0-ea" | ||
| } | ||
| ] | ||
| ] No newline at end of file |
There was a problem hiding this comment.
Missing trailing newline at end of file
ea/linux/x86_64.json and ea/macosx/aarch64.json lost their trailing newlines in this update (\ No newline at end of file shown in both diffs). The other 10 files in this PR retain proper newline endings. While JSON parsers typically tolerate this, it breaks POSIX file-format compliance and will create noisy future diffs.
Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!
Automated changes by create-pull-request GitHub action