Release r3.2 (Fall25 M4)

[bigludo7]

What type of PR is this?

Add one of the following kinds:

• subproject management

What this PR does / why we need it:

Publication of Fall'25 M4 public release of number-verification v2.1.0

Which issue(s) this PR fixes:

Fixes #214

Special notes for reviewers:

Changelog input

 release-note

Additional documentation

This section can be blank.

docs

[github-actions]

🦙 MegaLinter status: ✅ SUCCESS

Descriptor	Linter	Files	Fixed	Errors	Elapsed time
✅ ACTION	actionlint	2		0	0.01s
✅ API	spectral	1		0	1.56s
✅ GHERKIN	gherkin-lint	2		0	0.76s
✅ REPOSITORY	git_diff	yes		no	0.0s
✅ REPOSITORY	secretlint	yes		no	0.74s
✅ YAML	yamllint	1		0	0.38s

See detailed report in MegaLinter reports

MegaLinter is graciously provided by

[hdamker]

@bigludo7 please clarify the status of #94, close or set to draft if not part Fall25 (what I suppose) to create a clear situation for the release reviewers.

[bigludo7]

Thanks @Kevsy - I've commited your 2 requests.

[fernandopradocabrillo]

@bigludo7 in sim-swap @hdamker commented to go back to the previous model camaraproject/SimSwap#229 (comment)

we should do the same here

[bigludo7]

@bigludo7 in sim-swap @hdamker commented to go back to the previous model camaraproject/SimSwap#229 (comment)
we should do the same here

But for me, @fernandopradocabrillo, the request in the order was for the required section and not the properties section. Do I miss something?

[fernandopradocabrillo]

@bigludo7 in sim-swap @hdamker commented to go back to the previous model camaraproject/SimSwap#229 (comment)
we should do the same here

But for me, @fernandopradocabrillo, the request in the order was for the required section and not the properties section. Do I miss something?

@bigludo7 now you got me, I though the problem was the order of the properties because they are not aligned with the examples

[bigludo7]

@bigludo7 in sim-swap @hdamker commented to go back to the previous model camaraproject/SimSwap#229 (comment)
we should do the same here

But for me, @fernandopradocabrillo, the request in the order was for the required section and not the properties section. Do I miss something?

@bigludo7 now you got me, I though the problem was the order of the properties because they are not aligned with the examples

Let ask to our Guru - Herbert are we good to go for this one for M4 ? the required section order for the ErrorInfo is good but not the properties sorting. Thanks for guidance.

[hdamker]

Let ask to our Guru - Herbert are we good to go for this one for M4 ? the required section order for the ErrorInfo is good but not the properties sorting. Thanks for guidance.

@bigludo7 @fernandopradocabrillo

The order should be same in

• ErrorInfo.required
• ErrorInfo.properties
• and all examples using these schema

The correct order is status -> code -> message.

The reference is now in https://github.com/camaraproject/Commonalities/pull/517/files (the fix which aligns the order with the API Design Guide and which will go into Commonalities r3.4.)

You had exactly the right order in v2.0.0 of number-verification.

To avoid confusion of developers about an unnecessary change between NumberVerification v2.0.0 and v2.1.0 I strongly recommend that you fix the order also in ErrorInfo.properties before the M4 release, so that it is again the same as in v2.0.0

[bigludo7]

@fernandopradocabrillo @hdamker I reversed the order. A new PR was not required as main was in the right order.

[Kevsy]

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)