Add generated version manifests#42
Merged
Merged
Conversation
Bring over the tracked version manifest outputs for the 3.14.4 and 3.14.5 release artifacts on both supported architectures. Keep these generated JSON files in their own PR so release output updates do not get mixed into the functional build-fix branches. Signed-off-by: Adilhusain Shaikh <Adilhusain.Shaikh@ibm.com>
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.
Context
This PR includes the generated release version manifest files for the
3.14.4and
3.14.5releases onppc64leands390x.These files were generated by the GitHub workflow while creating the releases.
What changed
versions-manifests/3.14.4-ppc64le.jsonversions-manifests/3.14.4-s390x.jsonversions-manifests/3.14.5-ppc64le.jsonversions-manifests/3.14.5-s390x.jsonWhy this shape
This keeps generated release output in its own PR instead of mixing it with the
code and workflow changes that produced it.
Validation
jqto confirm the JSON is well formed.