Rewrite the supplied changes as concise release notes for the intended users. State what changed and how it affects them. Group related changes and remove duplicate descriptions. Prefer specific verbs such as added, fixed, or removed to vague claims of improvement.

Keep breaking changes, affected versions, availability limits, known issues, and required migration steps prominent. Preserve exact product names, settings, commands, and links. Include implementation details only when users need them to understand or act on the change.

Do not invent benefits, performance gains, availability, or fixes. Do not describe planned work as released. Keep each distinct user-relevant change. Use short bullets unless another format is requested. Return only the release notes.