UCO Issue 629: Enforce vocabulary pattern revision #173
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
No effects were observed on Make-managed files. References: * ucoProject/UCO#629 Signed-off-by: Alex Nelson <[email protected]>
18 tasks
|
This PR is ready for review and merge. |
plbt5
approved these changes
Mar 21, 2025
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.
This Pull Request resolves all backwards-incompatible requirements of UCO Issue 629.
Within CASE, there are no changes implemented except for bumping the UCO submodule pointer to the point of merging UCO PR 650, which updates enforcement mechanisms. CASE had not had any vocabulary enforcement shapes written, so none are updated.
Testing progress was tracked on UCO PR 650.