Merged
Conversation
grgpapadopoulos
previously approved these changes
Jun 26, 2025
26 tasks
grgpapadopoulos
previously approved these changes
Jul 16, 2025
jlurien
requested changes
Jul 18, 2025
Contributor
jlurien
left a comment
There was a problem hiding this comment.
On behalf of @camaraproject/release-management_reviewers
- Review suggestions and comments
- "Nonce " in the info.title for blockchain-public-address-validation is not coherent with the rest of references to the official name for this API (Copnfluence, changelog....), is there a reason to have this difference in title?
documentation/API_documentation/blockchain-public-address-API-Readiness-Checklist.md
Outdated
Show resolved
Hide resolved
documentation/API_documentation/blockchain-public-address-validation-API-Readiness-Checklist.md
Outdated
Show resolved
Hide resolved
documentation/API_documentation/blockchain-public-address-validation-API-Readiness-Checklist.md
Outdated
Show resolved
Hide resolved
documentation/API_documentation/blockchain-public-address-validation-API-Readiness-Checklist.md
Outdated
Show resolved
Hide resolved
documentation/API_documentation/blockchain-public-address-validation-API-Readiness-Checklist.md
Outdated
Show resolved
Hide resolved
Co-authored-by: Jose Luis Urien <jlurien@gmail.com>
Co-authored-by: Jose Luis Urien <jlurien@gmail.com>
…dation-API-Readiness-Checklist.md Co-authored-by: Jose Luis Urien <jlurien@gmail.com>
…dation-API-Readiness-Checklist.md Co-authored-by: Jose Luis Urien <jlurien@gmail.com>
…dation-API-Readiness-Checklist.md Co-authored-by: Jose Luis Urien <jlurien@gmail.com>
Collaborator
Author
I will take off "nonce" from API Title |
jlurien
approved these changes
Jul 28, 2025
Contributor
jlurien
left a comment
There was a problem hiding this comment.
Approved on behalf of @camaraproject/release-management_reviewers, next steps:
- PR merged (by API repository codeowner)
- Release created within GitHub (by API repository codeowner)
- Release Tracker updated (with creation date of the release and the release tag link)
grgpapadopoulos
approved these changes
Jul 29, 2025
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
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.
What type of PR is this?
What this PR does / why we need it:
Release 2.1 (Release candidate) PR for Blockchain Public Address APIs within Fall25 MetaRelease (M3)
Which issue(s) this PR fixes:
BlockChain Public Address:
Fixes #81
Fixes #82
Fixes #83
Fixes #84
FIxes #85
BlockChain Public Address Validation:
Fixes #88
Fixes #89
Fixes #90
Fixes #91
FIxes #92
Special notes for reviewers:
BlockChain Public Address:
Issue #81 is already covered in PR #99
Issue #82 is covered in this PR
Issue #83 is already covered in PR #100
Issue #84 is already covered in PRs #76, #95 and #97
Issue #85 is already covered in PR #101
BlockChain Public Address Validation:
Issue #88 is already covered in PR #102
Issue #89 is covered in this PR
Issue #90 is already covered in PR #103
Issue #91 is already covered in PR #76
Issue #92 is already covered in PR #104
Changelog input
Additional documentation
N/A
Additional documentation
N/A