docs: prepare changelog for v2.1.0-dusseldorf release

[nanotaboada]

Summary

• Update CHANGELOG.md: promote [Unreleased] to [2.1.0 - dusseldorf] - 2026-03-29

Test plan

• CI passes
• Merge to master
• Push tag v2.1.0-dusseldorf to trigger CD

🤖 Generated with Claude Code

Summary by CodeRabbit

• Documentation

  • Version 2.1.0 "dusseldorf" release documented in changelog (March 29, 2026).

• Chores

  • Code quality tooling configuration updated for enhanced analysis coverage.

[coderabbitai]

Warning

Rate limit exceeded

@nanotaboada has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 15 minutes and 39 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 15 minutes and 39 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: c3ad86e3-c675-4f06-9c9a-b5acee9a7805

📥 Commits

Reviewing files that changed from the base of the PR and between 29e11be and 69e8c7e.

📒 Files selected for processing (1)

• CHANGELOG.md

Walkthrough

The CHANGELOG.md file is updated to document version 2.1.0 (dusseldorf) released on 2026-03-29. SonarCloud configuration changes are recorded, transitioning from sonar-project.properties to .sonarcloud.properties with expanded CPD exclusion coverage.

Changes

Cohort / File(s)	Summary
Changelog and Documentation CHANGELOG.md	Added version 2.1.0 release entry with updated SonarCloud configuration details: transitioned from sonar-project.properties to .sonarcloud.properties and expanded CPD exclusions from test files and PlayerRequestModelValidator to include migrations, generated code, and repetitive production files.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 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 53 characters (well under 80), and clearly describes the changelog update for the v2.1.0-dusseldorf 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/2.1.0-dusseldorf

• 🛠️ 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

---

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.}

[nanotaboada]

@coderabbitai review

[coderabbitai]

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (1)

CHANGELOG.md (1)

45-47: Restore the [Unreleased] section template before the new release block.

[Unreleased] is currently empty. Keep the standard subsections (Added, Changed, Fixed, Removed) so future changes have the expected structure immediately after release cut.

Proposed doc fix

 ## [Unreleased]
 
+### Added
+
+### Changed
+
+### Fixed
+
+### Removed
+
 ---
 
 ## [2.1.0 - dusseldorf] - 2026-03-29

As per coding guidelines, "Update CHANGELOG.md [Unreleased] section (Added / Changed / Fixed / Removed) before committing".

🤖 Prompt for AI Agents

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

In `@CHANGELOG.md` around lines 45 - 47, Restore the standard [Unreleased] section
above the new release block by inserting a top-level "[Unreleased]" heading
followed by the four standard subsections "Added", "Changed", "Fixed", and
"Removed" (each as empty bullet or subsection) immediately before the existing
"## [2.1.0 - dusseldorf] - 2026-03-29" release heading so the file contains an
"[Unreleased]" section with those four subsections ready for future entries.

🤖 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: Update the bottom link map to reflect the new release: change the
[unreleased] link to compare from the new tag (use v2.1.0-dusseldorf...HEAD),
and add a new link entry for [2.1.0 - dusseldorf] that compares the previous
release tag to v2.1.0-dusseldorf (e.g., v2.0.0...v2.1.0-dusseldorf); ensure the
link labels match the headings exactly ([unreleased] and [2.1.0 - dusseldorf]).

---

Nitpick comments:
In `@CHANGELOG.md`:
- Around line 45-47: Restore the standard [Unreleased] section above the new
release block by inserting a top-level "[Unreleased]" heading followed by the
four standard subsections "Added", "Changed", "Fixed", and "Removed" (each as
empty bullet or subsection) immediately before the existing "## [2.1.0 -
dusseldorf] - 2026-03-29" release heading so the file contains an "[Unreleased]"
section with those four subsections ready for future entries.

🪄 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: fd471272-ca18-4abe-ab4f-1c8704e20d03

📥 Commits

Reviewing files that changed from the base of the PR and between 10bae34 and 29e11be.

📒 Files selected for processing (1)

• CHANGELOG.md

[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