docs(changelog): prepare release notes for v1.1.2-drogba#107
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
WalkthroughUpdated version-bump detection rules to explicitly identify breaking changes (BREAKING, BREAKING CHANGE:, or ! suffix) as major bumps and narrow minor bumps to true API additions. Populated the Unreleased section structure and created the 1.1.2 release entry documenting PlayerRequest validation and updated HTTP status behavior (422 for validation failures). ChangesRelease Documentation & Rules
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~4 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 2✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #107 +/- ##
=======================================
Coverage 84.88% 84.88%
=======================================
Files 6 6
Lines 172 172
=======================================
Hits 146 146
Misses 26 26 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
46c33d2 to
d8f6c69
Compare
Summary
/pre-releasecommand's minor/patch bump rule withgo-samples-gin-restful:### Addedentries only trigger a minor bump when they introduce a new endpoint, request parameter, or client-visible API response; test additions and internal tooling qualify as patchv1.1.2-drogba(patch): field-level validation via thevalidatorcrate and six new integration tests covering 422 responses for POST and PUTWhat's included in this release
PlayerRequestpayloads (validatorcrate,#97): required string fields must be non-empty;squad_numbermust be in range 1–99#97)/playersand PUT/players/squadnumber/{squad_number}now return422 Unprocessable Entityfor field validation failures;400 Bad Requestreserved for malformed JSON / wrongContent-Type(#94,#97)Test plan
[Unreleased]is empty,[1.1.2 - Drogba]section is present with today's date🤖 Generated with Claude Code
Summary by CodeRabbit
Documentation
Chores