Fixing schemas update to 1.1.0#5
Closed
LittleCoinCoin wants to merge 2 commits intoschemas-updatefrom
Closed
Conversation
added 2 commits
May 14, 2025 12:10
**Major** The subfields definitions for either indicating a local dependency or a remote were lacking the proper json `"type":"object"`
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.
This pull request faélls within the scope of #3 which were an attempt at updating the schemas. Unfortunatly, the validation failed and broke the deployment. After the validation and deployment workflows were separated in #4 to enable validation within PRs, we are now modifying the
hatch_pkg_metadata_schema.jsonfile to fix its structure.Schema fixing:
typeproperty to allow more flexible object definitions by adding additional nestedtypeobjects within theoneOfarray.format: "path"which doesn't exist