Release r1.2 (Fall'25 M4)#33
Conversation
|
I have just created this PR by the M4 deadline 2025-08-31. Thanks. |
@ToshiWakayama-KDDI I'm sorry, on Friday I was travelling back from 3GPP SA5. |
|
@ToshiWakayama-KDDI I can not add text in a review or modify the files apparently, at least I wasn't able to. SO I live my comment here. OAS file (YAML), line 28, in he image URL the release number must be updated from r1.1 to r1.2 |
No worries. So, you visited Gothenburg, didn't you? Thank you, @FabrizioMoggio, for pointing it out. I will correct the image URL. Probably Fill-in, too. Best, |
r1.1 -> r1.2
Yes indeed :-) a very nice town. |
|
(Note we're checking on the linting error, which believes you have too many scenarios - even though there are only 21 which should be ok) |
Co-authored-by: Kevin Smith <Kevsy@users.noreply.github.com>
Co-authored-by: Kevin Smith <Kevsy@users.noreply.github.com>
Co-authored-by: Kevin Smith <Kevsy@users.noreply.github.com>
Wrong x-correlator new format PR
I have just done this. Thanks. |
@Kevsy @ToshiWakayama-KDDI @FabrizioMoggio The linting configuration was fixed temporarily (the final update will be decided in Commonalities) - the Megalinter check is clean now |
Great! Thank you so much, @rartych . Actually, when I finished the commits above, I did not see any linting errors, so, I guessed some updates had been made for the admin side. So, I think we will be ready to go, once Codeowners approve. @fernandopradocabrillo , @GillesInnov35 , please review and approve this PR. Best, |
|
Hi @fernandopradocabrillo , @GillesInnov35 , cc @FabrizioMoggio , It was found that externalDocs object is missing in the kyc-match yaml, so, please wait for your review/approval. I will add it right now. Best regards, |
Fixed the order of two lines (version, commonalities version)
|
Hi @fernandopradocabrillo , @GillesInnov35 , cc @FabrizioMoggio ,
I think all done now, so, please review the PR and approve. Best regards, |
Kevsy
left a comment
There was a problem hiding this comment.
Approved on behalf of Release Management 👏
Next steps for the team:
- 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)
|
Great! Thanks very much, @Kevsy . Hi @fernandopradocabrillo , @GillesInnov35 . We need your approval (at least, either of you) to proceed with this PR, so, please. Many thanks, |
Done. Thanks @ToshiWakayama-KDDI for taking care of this PR |
|
Allow me to merge the PR right now, please, though we have not got Gilles' approval, as we do not have time for the M5 deadline. Many thanks, |
What type of PR is this?
What this PR does / why we need it:
Publication of Fall'25 M4 public release of kyc-match v0.4.0
Which issue(s) this PR fixes:
Fixes # N/A
Special notes for reviewers:
Before creating this PR, there was an error in the test scenarios (.feature file) detected by the centralised linting tool. As we are not sure if it is really an error, we have asked Commonalities about the error (Discussion #519 camaraproject/Commonalities#519 ) and this PR is created with the test scenario (.feature file) kept as is. ( @hdamker as Release Management is awere of it.)
Changelog input
Additional documentation
None