Pre-release r2.1 for consent-info v0.2.0-rc.1#46
Conversation
🦙 MegaLinter status: ✅ SUCCESS
See detailed report in MegaLinter reports |
|
@camaraproject/release-management_reviewers Hi team 😊, Just a friendly reminder to take a look at this PR when you have a moment. It contains the pre-release r2.1 for consent-info v0.2.0-rc.1 including updates to the API versioning, documentation, and test coverage. All checks are passing, and reviewers from the code-owners have already approved. Thanks in advance for your time! 🙏 |
Add r2.1 pre-release information with links to consent-info v0.2.0-rc.1 documentation (YAML, ReDoc, Swagger) following the extended release-info campaign template format.
🦙 MegaLinter status: ✅ SUCCESS
See detailed report in MegaLinter reports |
@jpengar that's correct for the upcoming release process. The current workflow would do it only after the release ... so I needed to add it already here, see 308f35e. |
hdamker
left a comment
There was a problem hiding this comment.
Looks perfect from ReleaseManagement perspective - sorry for the delay!
@camaraproject/consent-info_codeowners the PR needs one renewed codeowner approval due to the commit of the README.md update.
What type of PR is this?
Add one of the following kinds:
What this PR does / why we need it:
This pull request documents the pre-release of consent-info API v0.2.0-rc.1 (r2.1), introducing new features and updates to improve user experience and clarity in consent management. The most significant changes include the addition of a callback URL parameter, updated status terminology, expanded test coverage, and updates to documentation and versioning.
CHANGELOG.md, summarizing the introduction of consent-info v0.2.0-rc.1.API_documentation/consent-info-API-Readiness-Checklist.mdto reflect the new version (v0.2.0-rc.1), new release (r2.1), and updated references to Commonalities r3.4.consent-info.yamlto version 0.2.0-rc.1 and changed the server URL to match the new version.NOTE: The README release information section is not modified because it is automatically synchronized by the CAMARA project administration
Which issue(s) this PR fixes:
Fixes #39
Special notes for reviewers:
This new API release is not planned to be part of any meta-release
Changelog input
Additional documentation