You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
cbd74ea fixed the password-rule fixture, but the birthYear bump
2000 → 2012 introduced a new failure: 2012 is age 14, which
triggers the GDPR-K parental-consent gate (requires `parentEmail`).
Tests that don't pass `parentEmail` get 400 with
`"Konta dla osób poniżej 16 lat wymagają zgody rodzica."`.
2010 is exactly age 16 (today minus 16 years). The server check
is `< 16` (strict), so 16-year-olds bypass the parent-email
requirement while still passing my G-01 server clamp
`min(CURRENT_YEAR - 16) = 2010`.
Bumped birthYear 2012 → 2010 in all 7 e2e specs + the two
helper-fallback `?? 2012` defaults. Tests that explicitly want
to verify the parent-email flow still pass `parentEmail`
explicitly so they're unaffected.
Verified locally:
- POST /api/auth/register with birthYear 2010 returns
`{"ok":true,"ageBucket":"16-plus","needsConsent":false}`
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
0 commit comments