chore(release): v2.0.0-corner

[nanotaboada]

Summary

• Promotes [Unreleased] CHANGELOG entries to [2.0.0 - corner] - 2026-03-29
• Covers breaking changes from feat(api): migrate id to UUID, adopt squadNumber as natural key #550 (UUID migration, squadNumber natural key) plus chore PRs chore(github): update issue templates and add PR template #552 and chore(config): add .envrc for automatic nvm version switching #553
• Resets [Unreleased] section to empty template
• Updates README Releases section with the full branch-based release workflow

Pre-Release Checklist

• Release branch created from master
• CHANGELOG.md updated with release notes
• Changes committed and pushed on the release branch

🤖 Generated with Claude Code

---

This change is 

Summary by CodeRabbit

• Documentation
  • Standardized changelog layout with explicit release header template and reorganized sections for consistency
  • Rewrote release workflow into a multi-step process including creating a release branch, updating changelog, opening/merging a release PR, then tagging from main
  • Added a detailed pre-release checklist covering branch creation, changelog updates, PR flow, tag formatting/validation, and CD trigger
  • Generalized release artifact tagging (templated version/term) and expanded CD action descriptions

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 359ba78e-4cc0-4cb0-9007-65b9719fe9c4

📥 Commits

Reviewing files that changed from the base of the PR and between 5d5ffef and a2f6c26.

📒 Files selected for processing (1)

• CHANGELOG.md

🚧 Files skipped from review as they are similar to previous changes (1)

• CHANGELOG.md

---

Walkthrough

Updates release documentation and changelog: adds placeholder subsections in the Unreleased changelog, reorganizes the 2.0.0 entry, and replaces the README's single-step tag workflow with a multi-step release process (create release branch, update changelog, open/merge release PR, create annotated tag) plus a pre-release checklist and templated tag naming.

Changes

Cohort / File(s)

Summary

Release documentation CHANGELOG.md, README.md

CHANGELOG: added empty category headers under Unreleased, removed some subsections from the 2.0.0 entry, added separator and updated release header template and "How to Release" task list. README: replaced single-tag creation with a multi-step "Create a Release" workflow (create release/vX.Y.Z-term branch, update/commit changelog on branch, open/merge release PR into master, create annotated vX.Y.Z-term tag from master), expanded pre-release checklist, and generalized CD/docker tag templates to :X.Y.Z and :term.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Possibly related PRs

• feat: implement tag-based release workflow (#458) #475: Changes release workflow, changelog and README to adopt branch-based release flow and templated tag/docker naming.

🚥 Pre-merge checks | ✅ 2

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	Title follows Conventional Commits format (chore:), is 29 characters (well under 80), and clearly describes the v2.0.0-corner 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-corner

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (33bf567) to head (a2f6c26).
⚠️ Report is 5 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff            @@
##            master      #554   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            5         5           
  Lines          128       128           
  Branches        20        20           
=========================================
  Hits           128       128           

Components	Coverage Δ
Services	100.00% <ø> (ø)
Controllers	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: 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 `@README.md`:
- Around line 323-386: CHANGELOG.md's release instructions must be updated to
match the branch-based workflow documented in README.md: replace the current
direct-commit-and-tag steps with the branch → PR → merge → create annotated tag
after merge flow, ensure the checklist items mirror README's Pre-Release
Checklist (create release branch from master, update CHANGELOG, push branch,
merge PR, create/push tag after merge), and keep the same tag naming convention
`vX.Y.Z-term` and the note about valid "term" values (football terminology list)
so both files give identical guidance.
- Around line 323-376: The CD workflow currently triggers on tags matching
v*.*.*-* with no safeguard that the tag commit is on master; add a runtime
verification step early in the workflow (before build/publish steps) that checks
the tag's commit is part of master (for example use git branch -r --contains
<tag-or-GITHUB_SHA> or the GitHub API to confirm the commit is reachable from
refs/heads/master) and fail the job with a clear error if it is not; reference
the tag pattern v*.*.*-* and the master branch in the check so the workflow only
proceeds when the tag points to a commit contained in master.

🪄 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: ff9db1e2-088c-458c-8cd6-8e0008939d18

📥 Commits

Reviewing files that changed from the base of the PR and between b27a0c4 and 5d5ffef.

📒 Files selected for processing (2)

• CHANGELOG.md
• README.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