Update signature files and signature generation #276
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
KyleAure
added
documentation
KyleAure
changed the title
otaviojava
approved these changes
Sep 26, 2023
njr-11
approved these changes
Sep 26, 2023
KyleAure
force-pushed
the
267-milestone-signatures
branch
from
1e11541 to
79af223
Compare
|
Second commit after approval was to rebase and further update the signature files with changes to API that happened after original commit. I'll go ahead and merge this PR with the prior approval. |
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.
For #267
Wait to do the final signature file update until all changes to API signatures updates are finalized for milestone 1 release.
This PR is a placeholder for that work.