UCO Issue 586: Bump UCO to current state of develop
#154
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#586 * ucoProject/UCO#609 Signed-off-by: Alex Nelson <[email protected]>
ajnelson-nist
changed the title
developdevelop
|
This PR is ready for review and merge. |
plbt5
approved these changes
Jun 18, 2024
ajnelson-nist
added a commit
to casework/casework.github.io
that referenced
this pull request
Jun 18, 2024
A follow-on patch will regenerate Make-managed files. References: * ucoProject/UCO#586 * casework/CASE#154 Signed-off-by: Alex Nelson <[email protected]>
ajnelson-nist
added a commit
to casework/casework.github.io
that referenced
this pull request
Jun 18, 2024
References: * ucoProject/UCO#586 * casework/CASE#154 Signed-off-by: Alex Nelson <[email protected]>
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 PR does not require committee processing for merging. It should pass CI and receive an approving review, though.
This PR is part of delivering UCO Issue 586 via the CASE website.