Generate a full release package for range v1.3.0..HEAD (current version 1.3.0). Classify this git log, flag breaking changes with migration hints, suggest the next semver, and give a READY / READY-WITH-NOTES / NEEDS-REVIEW verdict.

[paste git log here]

Release Package

1. Summary

| Field | Value | |---|---| | Range | v1.3.0..HEAD | | Total commits | 8 | | Suggested version | 2.0.0 (major) | | Breaking changes | 1 | | Release readiness | READY-WITH-NOTES |

2. Changelog (Keep-a-Changelog)

Added

• Dark mode toggle.

Changed

• BREAKING: Auth endpoint /auth/login response shape changed.

Fixed

• Resolved a crash on empty cart.
• Handled null coupon codes at checkout.

3. Release Notes (human-friendly)

Dark mode is here — plus a cleaner, more reliable checkout.

Highlights

• You can now switch the whole app to dark mode with a single toggle.
• Checkout is more robust: empty carts no longer crash; missing coupon codes are handled safely.

Breaking change for API consumers /auth/login now returns { token, expiresIn } instead of { token }.

4. Breaking Changes & Migration

| Change | Impact | Migration hint | |---|---|---| | /auth/login response shape | API clients expecting { token } only | Update clients to read `tok

5. Release Readiness Checklist

| Item | Status | Notes | |---|---|---| | Breaking changes documented | done | Migration hint provided | | Version determined | done | 2.0.0 (major) | | Changelog complete | done | | | Release notes written | done | | | Tests passing | needs-manual-check | Verify CI is green | | Rollback plan identified | needs-manual-check | Confirm rollback steps |

6. Needs Attention

• Breaking change requires coordinated communication to API consumers.

7. Release JSON

{
  "range": "v1.3.0..HEAD",
  "total_commits": 8,
  "version": { "current": "1.3.0", "suggested": "2.0.0", "bump_type": "major" },
  "release_readiness": "READY-WITH-NOTES",
  "counts": { "features": 2, "fixes": 2, "breaking": 1, "reverts": 0, "noise_excluded": 3, "flagged_risky": 0 }
}