docs(changelog): release v2.0.0 Capello

[nanotaboada]

This change is 

Summary by CodeRabbit

• Breaking Changes
  • Player endpoints now use squad number instead of player ID for update and delete operations
  • Asynchronous service methods have been renamed to align with the new squad number-based approach

[coderabbitai]

Walkthrough

This change documents the release of version 2.0.0 "Capello" with three breaking changes: replacing UUID-based player endpoints with squad-number-based endpoints in PUT and DELETE operations, and renaming corresponding async service methods accordingly.

Changes

Cohort / File(s)	Summary
Release Documentation CHANGELOG.md	Added release notes for version 2.0.0 documenting three breaking changes: PUT and DELETE endpoints migrating from player UUID to squad number as the natural key, and async service method renames (update_async→update_by_squad_number_async, delete_async→delete_by_squad_number_async).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• PR #502: Implements the breaking changes documented in this changelog by switching player endpoints and async service methods from UUID-based to squad-number-based signatures.

🚥 Pre-merge checks | ✅ 2

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title follows Conventional Commits format with 'docs:' prefix, is under 80 characters (39 chars), and accurately describes the changelog update for v2.0.0 Capello release.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ 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 release/v2.0.0-capello

• 🛠️ sync documentation: Commit on current branch
• 🛠️ sync documentation: Create PR
• 🛠️ enforce http error handling: Commit on current branch
• 🛠️ enforce http error handling: Create PR
• 🛠️ idiomatic review: Commit on current branch
• 🛠️ idiomatic review: Create PR
• 🛠️ verify api contract: Commit on current branch
• 🛠️ verify api contract: Create PR

📝 Coding Plan

• Generate coding plan for human review comments

---

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

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

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[codecov]

Codecov Report

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

Additional details and impacted files

@@            Coverage Diff            @@
##            master      #525   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            3         3           
  Lines          111       111           
=========================================
  Hits           111       111           

Components	Coverage Δ
Services	100.00% <ø> (ø)
Routes	100.00% <ø> (ø)

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[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 47: The changelog header "## [2.0.0 - Capello]" lacks a matching
reference in the footer and the [unreleased] comparison still points to
v1.1.0-bielsa; update CHANGELOG.md by adding a release reference link for
"[2.0.0 - Capello]" in the links footer (e.g., define [2.0.0 - Capello]:
<compare URL or tag>) and adjust the "[unreleased]" link so it compares from the
correct previous tag (replace v1.1.0-bielsa with the proper base tag) to restore
correct release navigation.

🪄 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: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 476ddff2-8d34-43ca-a859-4644356a7e7b

📥 Commits

Reviewing files that changed from the base of the PR and between fc081b6 and 67498fe.

📒 Files selected for processing (1)

• CHANGELOG.md

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Add missing changelog link references for the new release section.

You added ## [2.0.0 - Capello], but the footer doesn’t define [2.0.0 - Capello], and [unreleased] still compares from v1.1.0-bielsa. This leaves release navigation incorrect after 2.0.0.

📌 Suggested patch

-[unreleased]: https://github.com/nanotaboada/python-samples-fastapi-restful/compare/v1.1.0-bielsa...HEAD
+[unreleased]: https://github.com/nanotaboada/python-samples-fastapi-restful/compare/v2.0.0-capello...HEAD
+[2.0.0 - Capello]: https://github.com/nanotaboada/python-samples-fastapi-restful/compare/v1.1.0-bielsa...v2.0.0-capello
 [1.1.0 - Bielsa]: https://github.com/nanotaboada/python-samples-fastapi-restful/compare/v1.0.0-ancelotti...v1.1.0-bielsa
 [1.0.0 - Ancelotti]: https://github.com/nanotaboada/python-samples-fastapi-restful/releases/tag/v1.0.0-ancelotti

🤖 Prompt for AI Agents

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

In `@CHANGELOG.md` at line 47, The changelog header "## [2.0.0 - Capello]" lacks a
matching reference in the footer and the [unreleased] comparison still points to
v1.1.0-bielsa; update CHANGELOG.md by adding a release reference link for
"[2.0.0 - Capello]" in the links footer (e.g., define [2.0.0 - Capello]:
<compare URL or tag>) and adjust the "[unreleased]" link so it compares from the
correct previous tag (replace v1.1.0-bielsa with the proper base tag) to restore
correct release navigation.