release v0.9.0

[mdfarhankc]

Summary

Cuts v0.9.0 — security hardening and polish since v0.8.0.

Breaking changes

• Lockout response is now 401 instead of 423 Locked. Clients branching on 423 to render a "locked" UI fall into the generic credentials path.
• Email lookup is now case-insensitive (lowercase + strip on create/update/lookup). Case-sensitive collations (MySQL default, MSSQL) need a one-off UPDATE fullauth_users SET email = LOWER(TRIM(email)) before upgrade.

Security

• Email normalization on create/update/lookup — Alice@X.com and alice@X.com can no longer register as separate accounts on case-sensitive collations.
• Lockout collapsed into generic 401 to remove the status-code enumeration signal.
• Opt-in PREVENT_REGISTRATION_ENUMERATION — /register returns a generic 202 regardless of whether the email was taken.

Fixed

• BearerBackend accepts any case of the Bearer scheme per RFC 7235.
• require_role tolerates a UserSchema with no roles field — clean 403 instead of 500.
• hash_password(..., algorithm="bcrypt") rejects > 72 UTF-8 bytes instead of silently truncating.
• SQLModel UserBase.hashed_password column is now Text, matching the SQLAlchemy adapter.
• FullAuthConfig validates passkey settings at construction time.

Docs / skill

• Rewrote the case-sensitivity note in the adapters reference.
• Added a 0.8.0 → 0.9.0 migrations section (email lowercase migration + SQLModel column type change).
• Three new skill references added during the release window: testing, troubleshooting, api-reference.

Test plan

• uv run ruff format --check . — clean
• uv run ruff check . — clean
• uv run pytest tests/ — 188 passed, 1 skipped
• CI matrix (3.10–3.14) passes on this PR
• After merge: gh release create v0.9.0 --target main triggers publish.yml → PyPI publish via OIDC
• uv pip install fastapi-fullauth==0.9.0 in a scratch venv imports cleanly

[coderabbitai]

Warning

Rate limit exceeded

@mdfarhankc has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 20 minutes and 40 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 20 minutes and 40 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: defaults

Review profile: CHILL

Plan: Pro

Run ID: d5557d4c-f9ee-434e-a5c8-89bc4e0530ad

📥 Commits

Reviewing files that changed from the base of the PR and between 975ba71 and ef92671.

⛔ Files ignored due to path filters (1)

• uv.lock is excluded by !**/*.lock

📒 Files selected for processing (5)

• CHANGELOG.md
• fastapi_fullauth/.agents/skills/fastapi-fullauth/references/adapters.md
• fastapi_fullauth/.agents/skills/fastapi-fullauth/references/migrations.md
• fastapi_fullauth/__init__.py
• pyproject.toml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch release/v0.9.0

---

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