Backfill changelog from releases

[koxudaxi]

Summary

• Regenerate CHANGELOG.md from published GitHub release notes
• Include all 48 non-draft releases, including the existing 0.6.0 entry and historical releases back to 0.0.1
• Exclude the draft 0.6.1 release

Checks

• git diff --check
• grep -c '^## \\[' CHANGELOG.md -> 48
• verified 0.6.1 is not included

Summary by CodeRabbit

• Documentation
  • Updated release notes: adjusted subsection heading levels in the 0.6.0 entry and appended full historical release entries for versions 0.5.4 → 0.0.1, each with dated headers, “What’s Changed” bullet lists, optional “New Contributors” subsections, and corresponding full-changelog comparison links to complete the history.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 495b8b20-ec83-4e72-ad9a-ffb020cff160

📥 Commits

Reviewing files that changed from the base of the PR and between bdcb484 and b930d09.

📒 Files selected for processing (1)

• CHANGELOG.md

---

Walkthrough

CHANGELOG.md headings for the 0.6.0 section were demoted (## → ###), and comprehensive historical release entries for versions 0.5.4 through 0.0.1 were appended, each including release title + tag URL, dated "What's Changed" bullets, optional "New Contributors", and "Full Changelog" compare links.

Changes

Cohort / File(s)	Summary
Changelog Documentation CHANGELOG.md	Adjusted 0.6.0 subsection headings from ## to ###; appended detailed historical release entries for 0.5.4 → 0.0.1 with dated headers, "What's Changed" lists, optional "New Contributors", and "Full Changelog" compare URLs. No code changes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Possibly related PRs

• Fix release followup workflows #576 — Also modifies CHANGELOG.md around the 0.6.0 changelog and related changelog generation/workflow adjustments.

Poem

🐇 I hopped through lines of changelog lore,

Letters and dates I carefully store,
From 0.5.4 back to 0.0.1's door,
A trail of releases, neat and more,
Carrots for history — hop, explore!

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the main change: backfilling the CHANGELOG.md with historical release information from published GitHub releases.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch backfill-release-changelog

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Review rate limit: 5/8 reviews remaining, refill in 17 minutes and 1 second.}

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

📚 Docs Preview: https://pr-577.fastapi-code-generator.pages.dev

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@CHANGELOG.md`:
- Line 128: Fix the typo in the CHANGELOG entry that currently reads "fix
inconsistance routers<>tags arrays by `@azdolinski` ..." by replacing
"inconsistance" with "inconsistency"; locate the bullet starting with "* fix
inconsistance routers<>tags arrays" in CHANGELOG.md (the PR entry text) and
update the word, then re-run the codespell/CI check to ensure the pipeline
passes.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 6920dbc8-1239-46db-9ea1-3207b8767706

📥 Commits

Reviewing files that changed from the base of the PR and between ed5b283 and 4bbc5de.

📒 Files selected for processing (1)

• CHANGELOG.md

[coderabbitai]

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@CHANGELOG.md`:
- Line 71: The repeated top-level headings "## What's Changed" and "## New
Contributors" in CHANGELOG.md should be demoted to subsection headings under
each release; replace each instance of "## What's Changed" and "## New
Contributors" with "### What's Changed" and "### New Contributors" respectively
so they are nested beneath the release heading, and apply this consistently to
every occurrence listed (e.g., the occurrences referenced around lines with the
strings "## What's Changed" and "## New Contributors"). Ensure you only change
those exact heading lines and keep the existing content beneath them intact so
markdownlint MD024 warnings are resolved.
- Line 156: Fix the obvious typos in the changelog bullets: replace the
misspelled token "requeststBody" with "requestBody" wherever it appears (e.g.,
the new bullet added for PR `#382`) and expand any truncated artifact like "bod…"
to the full word "body" so the entries read clearly; update the affected
bullets' text to use correct spelling and complete wording while preserving the
original meaning and PR attribution.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 5bc95e04-05d6-424a-9e62-d6dfd975cfa0

📥 Commits

Reviewing files that changed from the base of the PR and between 4bbc5de and bdcb484.

📒 Files selected for processing (1)

• CHANGELOG.md

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (ed5b283) to head (b930d09).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##              main      #577   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           17        17           
  Lines         1351      1351           
  Branches       139       139           
=========================================
  Hits          1351      1351           

Flag	Coverage Δ
unittests	100.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[github-actions]

Breaking Change Analysis

Result: No breaking changes detected

Reasoning: PR #577 only modifies CHANGELOG.md — it backfills historical release notes and fixes two heading levels in the existing 0.6.0 entry. No source code, templates, CLI options, default behaviors, dependencies, or error handling were changed. This is purely a documentation update with zero impact on the tool's functionality or output.

---

This analysis was performed by Claude Code Action