Raw view: Release Notes From a Changelog

No invisible, zero-width, or bidi-control characters detected.

Write release notes for {{PRODUCT_NAME}} {{VERSION}} from the raw changes below. Readers are {{AUDIENCE}} (for example, "developers integrating our SDK" or "end users of the web app"). They want to know what changed for them and what they must do; they do not care how the sausage was made.

<changelog>
{{CHANGELOG}}
</changelog>

<previous_notes>
{{PREVIOUS_NOTES}}
</previous_notes>

<previous_notes> is an earlier release's notes, if available, to match voice and structure. If empty, use the format below as-is.

Procedure:

1. Read every entry in <changelog> and classify it: `breaking`, `deprecation`, `feature`, `improvement`, `fix`, `security`, `internal`. Entries that are `internal` (refactors, CI, dependency bumps with no user-visible effect, test changes) are dropped from the notes; list them in the "Omitted" section so a reviewer can check your judgment.
2. Rewrite each kept entry from the user's point of view: what they can now do, what no longer happens, what they must change. Lead with the verb. "Export now includes archived projects" beats "Added archived flag to export query". Strip ticket IDs, author names, and internal component names unless the audience uses them.
3. Merge entries that describe one user-visible change across several commits. Split entries that bundle unrelated changes.
4. For every `breaking` and `deprecation` entry, write the required action: what to change, by when (if a removal date is given or implied), and the before/after if it is a code or config change. If the changelog does not say what the migration is, write `[migration steps needed]` rather than guessing.
5. For `security` entries, state the impact and the fixed version plainly; do not describe exploitation details.
6. Keep each bullet to one or two sentences. Link placeholders are allowed as `[docs]` where a reader would obviously want one.

Match the voice of <previous_notes> if provided: tense, person, level of formality, use of emoji (default: none).

## Output format

```
# {{PRODUCT_NAME}} {{VERSION}}
_Released YYYY-MM-DD_

## Breaking changes            (omit heading if none)
- **What changed.** Required action. Before/after if applicable.

## Deprecations                (omit if none)
- **What is deprecated.** Replacement. Removal timeline.

## Security                    (omit if none)

## New
- ...

## Improvements
- ...

## Fixes
- ...

## Upgrade notes               (only if any action is required; otherwise omit)
```

After the notes, add two sections for the reviewer only (not for publication):

**Omitted as internal** - the changelog entries you dropped, one per line.

**Needs confirmation** - entries whose classification or user impact you were unsure about, each with the question to answer.