Update Changelog

[tlohmar]

What type of PR is this?

Add one of the following kinds:

• subproject management

What this PR does / why we need it:

This is Release PR for release 2.1 containing version rc.1 of Dedicated Networks APIs. Release 2.1 is independent from the Meta-Release process.

Which issue(s) this PR fixes:

Fixes #69

Special notes for reviewers:

Changelog input

 release-note

Additional documentation

This section can be blank.

docs

[tanjadegroot]

Hi Thorsten,

your repository is enabled to use the automated release process. This would automatically create the Release Review PR, so this current PR should not need be done manually.

To activate the automated release process, please do a separate PR first on release-plan.yaml to update all fields according to your planned release.
It is recommended to an alpha release first on this new release cycle.
Also please check with all API teams that they baseline on Fall25 Commonalities and ICM, and what next release is planned. Your draft changelog keeps the network-qos-profles API as public (unchanged) while there are actually changes to that API planned.

• change the target_release_type to pre-release-alpha
• add the missing API
• update all the API data with targetted API versions and status.

Doing the PR on (just) release-plan.yaml creates a new issue, referred to as the Release Issue to be used for driving the automated release process by putting commands in the comment fields of this issue.

Next steps:

1. deactivate this PR by

• putting this PR in DRAFT mode (see "convert to draft" link in the right column)
• rename it to "Update Changelog" to avoid confusion
• NEVER merge this PR to main but keep it for now for text re-use later when reviewing the Changelog content in the Release Review PR

2. prepare and merge a dedicated PR for updating the release-plan.yaml

3. then go to the release issue and check the next possible actions for guidance.

With the new process you do not need to

• create branch for preparing the release: the /create-snapshot will create a dedicated branch
• touch the changelog file until after the /create-snapshot command succeeds. This command will create the Release Review PR automatically and includes an easy to update proposal for the Changelog as well.

You will be able to reuse text for the changelog in the Release Review PR as useful from this PR.

Hope this helps, it should simplify life once you get the hang of it.

Please do not hesitate to ask questions on the automation process on Zulip channel

@hdamker : FYI