@voltro/plugin-auth-social 0.86.0 → 0.87.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -2,7 +2,7 @@
2
2
 
3
3
  # @voltro/plugin-auth-social
4
4
 
5
- **First-party social login for the Voltro framework — Sign in with Google, GitHub and Apple. Mandatory PKCE (S256) + state, JWKS-verified ID tokens, a deliberate account-linking policy, and sessions issued through @voltro/plugin-auth. No identity vendor required.**
5
+ **First-party social login for the Voltro framework — Google, GitHub and Apple login; Discord, Twitch and Microsoft additions are built. Mandatory PKCE (S256) + state, JWKS-verified ID tokens, a deliberate account-linking policy, and sessions issued through @voltro/plugin-auth. No identity vendor required.**
6
6
 
7
7
  [📖 Documentation](https://docs.voltro.dev/docs/plugins/auth-social) · [voltro.dev](https://voltro.dev) · [Voltro Cloud](https://voltro.cloud)
8
8
 
@@ -20,7 +20,14 @@ Installation, guides, the full API reference, and examples all live in the
20
20
  **[Voltro documentation](https://docs.voltro.dev/docs/intro/getting-started)** — the single source of truth. This README is
21
21
  deliberately short so there is nothing here to drift out of date.
22
22
 
23
+ Opt-in same-ID guest promotion, signed browser confirmation and the durable
24
+ `@voltro/plugin-auth-social/web` client are **built**. See the docs for the
25
+ transaction/installed-port contract, confirmed device proof and recovery limits.
26
+ Existing-account conflicts require a separately confirmed merge.
27
+
23
28
  ## License
24
29
 
25
30
  Proprietary. © 2026 Voltro UG. Your use is governed by the
26
31
  [Terms of Service](https://voltro.cloud/legal/terms). See the bundled `LICENSE`.
32
+
33
+ The DataStore-backed identity adapter accepts the framework store and its transaction views directly. Provider-account lookup and unlink use a bounded canonical query (`take: 1`); creation-order listing uses the same store descriptor. Custom standalone identity stores retain their existing narrow contract.