Skip to content

Spring25 - M3 Milestone - Prepare r2.1#92

Merged
bigludo7 merged 34 commits intomainfrom
Prepare-r2.1
Feb 11, 2025
Merged

Spring25 - M3 Milestone - Prepare r2.1#92
bigludo7 merged 34 commits intomainfrom
Prepare-r2.1

Conversation

@bigludo7
Copy link
Collaborator

@bigludo7 bigludo7 commented Jan 16, 2025

What type of PR is this?

Add one of the following kinds:

  • subproject management

What this PR does / why we need it:

  • This PR implements the scope for Spring25
  • The PR updates all the file in terms of release number referring to r2.1 and version v1.13.0-rc.1
  • CHANGELOG.MD, READ.ME & Readiness check list updated version are provided

Which issue(s) this PR fixes:

Fixes camaraproject/Commonalities#91 camaraproject/Commonalities#93

Special notes for reviewers:

Changelog input

 release-note

Additional documentation

This section can be blank.

docs

@bigludo7 bigludo7 requested a review from a team January 16, 2025 20:45
@github-actions
Copy link

github-actions bot commented Jan 16, 2025

🦙 MegaLinter status: ✅ SUCCESS

Descriptor Linter Files Fixed Errors Elapsed time
✅ ACTION actionlint 2 0 0.03s
✅ OPENAPI spectral 1 0 1.64s
✅ REPOSITORY git_diff yes no 0.01s
✅ REPOSITORY secretlint yes no 0.71s
✅ YAML yamllint 1 0 0.32s

See detailed report in MegaLinter reports

MegaLinter is graciously provided by OX Security

bigludo7 and others added 2 commits January 20, 2025 11:23
Co-authored-by: Fernando Prado Cabrillo <fernando.pradocabrillo@telefonica.com>
…cklist.md

Co-authored-by: Fernando Prado Cabrillo <fernando.pradocabrillo@telefonica.com>
@hdamker
Copy link
Contributor

hdamker commented Jan 23, 2025

Two comments (I'm currently looking on the stable APIs from Fall24 to see which of them have breaking changes):

  • optional phoneNumber: either the phoneNumber is required or you need to add the text how the phoneNumber will be determined in case of 3-legged vs 2-legged. But as 3-legged doesn't make sense here, I would go with the conclusion in Update API-design-guidelines.md Commonalities#88 and revert the change. Or have I overseen something?
  • x-correlator: there will be the change coming with Commonalities 0.5.0-rc.1 with the validation pattern. I would recommend to for the final decision (see Allow zero-length strings in x-correlator header Commonalities#387) on the pattern before creating the release here.

Copy link
Contributor

@hdamker hdamker left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@bigludo7:
Several small changes suggested, most of them to correct the version number to 1.1.0-rc.1 (only within the server url v1rc1 is correct).

CHANGELOG.md Outdated

## one-time-password-sms 1.1.0-rc1

This is the first **pre-release** of the one-time-password-sms API version 1.1.0-rc1. It contains mainly alignments with the Commonalities 0.5.0 and the Release Management Guidelines.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
This is the first **pre-release** of the one-time-password-sms API version 1.1.0-rc1. It contains mainly alignments with the Commonalities 0.5.0 and the Release Management Guidelines.
This is the first **pre-release** of the one-time-password-sms API version 1.1.0-rc.1. It contains mainly alignments with the Commonalities 0.5.0 and the Release Management Guidelines.

Just curious: are there relevant changes to the API due to the "Release Management Guidelines". Or did you mean the Identity and Consent Management guidelines?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hello @hdamker - Yes I mean initially Identity and Consent Management but then as this API is not impacted to the new device/phoneNumber error we are not either impacted by Identity & Consent Management. I've removed mention to Identity and Consent Management & Release management to only keep Commonalities.

bigludo7 and others added 7 commits February 3, 2025 14:01
Co-authored-by: Herbert Damker <herbert.damker@telekom.de>
Co-authored-by: Herbert Damker <herbert.damker@telekom.de>
Co-authored-by: Herbert Damker <herbert.damker@telekom.de>
Co-authored-by: Herbert Damker <herbert.damker@telekom.de>
…cklist.md

Co-authored-by: Herbert Damker <herbert.damker@telekom.de>
…cklist.md

Co-authored-by: Herbert Damker <herbert.damker@telekom.de>
…cklist.md

Co-authored-by: Herbert Damker <herbert.damker@telekom.de>
bigludo7 and others added 11 commits February 3, 2025 14:04
…cklist.md

Co-authored-by: Herbert Damker <herbert.damker@telekom.de>
Co-authored-by: Herbert Damker <herbert.damker@telekom.de>
Co-authored-by: Herbert Damker <herbert.damker@telekom.de>
…cklist.md

Co-authored-by: Herbert Damker <herbert.damker@telekom.de>
Co-authored-by: Herbert Damker <herbert.damker@telekom.de>
Co-authored-by: Herbert Damker <herbert.damker@telekom.de>
Co-authored-by: Herbert Damker <herbert.damker@telekom.de>
…cklist.md

Co-authored-by: Herbert Damker <herbert.damker@telekom.de>
Co-authored-by: Herbert Damker <herbert.damker@telekom.de>
Remove release management in line 29
Update release version in line 29
@bigludo7
Copy link
Collaborator Author

bigludo7 commented Feb 3, 2025

Hello @hdamker
Thanks a lot for the review
All applied.

Copy link
Contributor

@hdamker hdamker left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good from Release Management perspective.

@bigludo7 There is one question open, which you haven't resolved for some reason.

Copy link
Contributor

@hdamker hdamker left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was a little bit too fast ... just have found one open point which should be corrected.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just have found one of my comments which are not yet done: The text in lines 18 to 20 need to be updated with the latest changes in ICM r2.2

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done - I've copied the text.

@hdamker
Copy link
Contributor

hdamker commented Feb 4, 2025

I will unblock the PR after the version issue within camaraproject/NumberVerification#164 (comment) is discussed and solved in Release Management, as the same applies also here for OTPValidation.

hdamker
hdamker previously approved these changes Feb 10, 2025
@bigludo7
Copy link
Collaborator Author

I will unblock the PR after the version issue within camaraproject/NumberVerification#164 (comment) is discussed and solved in Release Management, as the same applies also here for OTPValidation.

@hdamker I've applied camaraproject/ReleaseManagement#163

Change version in the path from v1 to v1.1.0-rc.1
Copy link
Contributor

@hdamker hdamker left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM - thanks for your patience and quick responses!

@bigludo7
Copy link
Collaborator Author

LGTM - thanks for your patience and quick responses!

Thanks for your review & guidance Herbert !

@bigludo7 bigludo7 merged commit 95c91ad into main Feb 11, 2025
2 checks passed
@bigludo7 bigludo7 deleted the Prepare-r2.1 branch February 11, 2025 10:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants