Create a release

Prepare and publish release v2.1.0 for the analytics project. Draft the release notes using merged PR titles and highlight breaking changes and migration steps, set the tag on the release-2.1 branch, and share the release URL with the support team and product manager for an approval check by Thursday afternoon.

Before I create the release, extract the merged PRs since v2.0.2, surface bug fixes that affect customers, and list any database migrations or config changes that require manual steps. Rewrite the release notes so a non-engineer product manager can understand the user impact and produce a two-line summary for the support KB.

I opened the release draft for v2.1.0 and the changelog area is empty though I expected several merged PRs. I might be pointing at the wrong branch or tag. Diagnose what likely went wrong and give the exact checks to run on the repo and branch, how to regenerate the changelog from merged PRs, and what to tell the product manager about timing if I have to recreate the draft.

Over the last four releases the release notes are sparse and approvals drag on, causing delayed deploys. Where are we losing authority and speed? Recommend one change to how we draft releases (who writes the first pass, what template to use, and a two-sentence process for PM approval) so releases are clearer and approved within 24 hours.