fix: complete ARM64 metadata target mappings - #33
Merged
Conversation
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
1 participant
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.
Complete the remaining Linux ARM64 mappings exposed by the v1.0.0 offline release suite.\n\n- recognize Temurin Linux aarch64 binaries in Java metadata\n- include Linux aarch64 in Java and Python metadata fixtures\n- include Linux ARM64 in Java and .NET lockfile fixtures\n\nThe preceding release run passed every CLI integration test, including Node and Go source validation, before exposing these core fixture gaps. Verification is delegated to GitHub Actions; no local or WSL build/test/runtime command was run.