chore: bump version to 2026.2.2, add changelog and update news (Task 7)
This commit is contained in:
@@ -0,0 +1,20 @@
|
||||
---
|
||||
title: "Domain Restriction & Branded Placeholder — Sign-Up Protection"
|
||||
date: "2026-05-27"
|
||||
version: "2026.2.2"
|
||||
summary: "Blocked sign-ups using @deckyvault.xyz email addresses in production and updated all auth form email placeholders to use the DeckyVault domain."
|
||||
---
|
||||
|
||||
### Domain Protection for Sign-Ups
|
||||
|
||||
New accounts can no longer be created with `@deckyvault.xyz` email addresses in production. This prevents unauthorized use of the DeckyVault brand domain — the domain owner is the only one who should be creating accounts with those addresses.
|
||||
|
||||
The restriction applies to all sign-up methods: email/password, one-time code (OTP), and social login via Google or Discord.
|
||||
|
||||
**What's NOT affected:**
|
||||
- Existing `@deckyvault.xyz` accounts continue to work normally — login, password reset, and OTP sign-in are all functional
|
||||
- Development builds still allow `@deckyvault.xyz` sign-ups for testing
|
||||
|
||||
### Branded Placeholder Text
|
||||
|
||||
All email input fields across web and mobile now show `you@deckyvault.xyz` as the default placeholder, replacing the generic `you@example.com`. This appears in the sign-up, login, and forgot password forms.
|
||||
Reference in New Issue
Block a user