Release r1.3 (Fall'25 M4)

[alpaycetin74]

What type of PR is this?

• subproject management

What this PR does / why we need it:

To release the first pre-release versions of Brand Registration and Verified Caller APIs.
In the process, the description of Verified Caller API is improved and occurrences of the confusing naming (Pre Announcement) is removed from the repository.

Which issue(s) this PR fixes:

Fixes #44

Special notes for reviewers:

Special notes for reviewers:
This PR adds no other changes on top of r1.2 other than the version adjustment and documentation improvements mentioned above.

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	2		0	3.08s
✅ GHERKIN	gherkin-lint	5		0	1.71s
✅ REPOSITORY	git_diff	yes		no	0.0s
✅ REPOSITORY	secretlint	yes		no	0.74s
✅ YAML	yamllint	2		0	0.61s

See detailed report in MegaLinter reports

MegaLinter is graciously provided by

[eric-murray]

@alpaycetin74
The latest releases of both Commonalities and ICM is r3.3. So you need to update the change log, and also the two API readiness checklists, to reflect that.

[alpaycetin74]

Thank you @eric-murray , I applied your comments.

[hdamker]

@alpaycetin74 Please update also the README, it is currently only mentioning pre-releases, and you will have here the public release of the first initial API version. Use examples from other APIs as a template, e.g. camaraproject/ConsentInfo#33

[alpaycetin74]

@alpaycetin74 Please update also the README, it is currently only mentioning pre-releases, and you will have here the public release of the first initial API version. Use examples from other APIs as a template, e.g. camaraproject/ConsentInfo#33

Thank you @hdamker , updated.

[Kevsy]

Hi @alpaycetin74 -almost there, you just need to complete #63 and then I can approve on behalf of release management

[alpaycetin74]

Hi @alpaycetin74 -almost there, you just need to complete #63 and then I can approve on behalf of release management

just closed, thank you. @Kevsy

[GillesInnov35]

Thanks

[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)