Public release r3.3

[jpengar]

What type of PR is this?

• subproject management

What this PR does / why we need it:

This is the release PR for the public release r3.3 (public release for Fall25) containing version v0.4.0 of ICM

Which issue(s) this PR fixes:

Fixes #275

Special notes for reviewers:

This PR includes all the changes agreed the ICM scope of the Fall25 meta-release.

• label fall25
• Meta-release Fall25 milestone

Changelog input

 r3.3 containing version v0.4.0 of ICM

Additional documentation

https://lf-camaraproject.atlassian.net/wiki/spaces/CAM/pages/36241429/Meta-release+Fall25
https://lf-camaraproject.atlassian.net/wiki/spaces/CAM/pages/14551399/Meta-release+Process#Commonalities-and-ICM

[rartych]

Proposal mentioned in #295 (review) is not addressed.
Maybe the description of changes in Release Notes can be extended or informative Wiki page can be created to help API consumers and providers understand the changes in ICM.

[jpengar]

Proposal mentioned in #295 (review) is not addressed. Maybe the description of changes in Release Notes can be extended or informative Wiki page can be created to help API consumers and providers understand the changes in ICM.

@hdamker's specific comments were indeed addressed in the same r3.2 PR in 75b09f6 commit. Following these comments, I attempted to write more descriptive sentences for the new topics added to the r3.3 changelog, as PR titles are not always sufficiently descriptive. @rartych Is there any topic in the changelog for which you would like more detail? Bear in mind that, apart from the new JWT Bearer flow, the other changes to ICM in this meta-release are not major and I understand that the changelog is not intended to be overly verbose.

[rartych]

@jpengar thanks for clarifications.
I agree that the changelog is not intended to be overly verbose, so let's go with the public release.
On request of TSC or Release Management team the Wiki page can be created summarizing changes that are important for API consumers and providers to avoid individually tracking changes in PRs. As the changes are rather not impacting API definitions, but should be condsidered when deploying APIs from Fall25 meta-release.