ci: pin main jar name in java dry-run check - #685
Merged
Conversation
kartikeya-27
approved these changes
Aug 17, 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.
The Java publish dry-run resolved the main jar with
ls build/libs/flexiq-*[0-9].jar. Every classifier jar also ends in a digit (-linux-x86_64.jar,-osx-aarch64.jar), so the glob matched six files,$jarbecame the whole list, and the firstunzip -pran against a platform jar — which is not multi-release, so the check aborted underset -e.Pins the main and sources jars by exact name and asserts each exists.
Pre-existing, not from the rename: the ambiguity arrived with the classifier jars in #510 (2026-07-24), and the last dry-run before today was 2026-06-27. Real tag pushes skip the step entirely (
if: inputs.dry-run), so releases through 0.22.0 were unaffected.