Fixing schema $id tagging to 1.3.4 #80
Merged
Conversation
This file contains 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
…g as 1.3.5, to ensure that the release is properly made? Otherwise, the current release 1.3.4 needs to be replaced)
cbizon
approved these changes
Apr 12, 2023
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.
The Git released files for v1.3.4 didn't update the $id fields in the two 'workflow' and 'operations' schemata files. This PR does this.
If the existing v1.3.4 release cannot be fully patched in situ, then fix the three schema identifier URI's to 1.3.5 then release the project as v1.3.5 (suggest that the flawed releases are removed from Git and otherwise deprecated in other contexts)