Changed #

• Removed voo_core dependency to make the package fully standalone

Fixed #

• Fixed OAuth code login endpoint from /auth/oauth/{provider}/code to /auth/oauth/{provider} to match backend API

Fixed #

• Fixed token refresh endpoint from /auth/refresh to /auth/refresh-token to match backend API

Fixed #

• Added missing OAuthProvider.authstack case to switch expression in example app
• Fixed nullable refreshToken type mismatch in exchangeCodeViaBackend() method

Added #

• OAuthProvider.authstack enum value for apps using AuthStack as their identity provider

Added #

• exchangeCodeViaBackend() method for routing OAuth code exchange through a custom backend API
  • Enables consumer apps to issue their own JWT tokens instead of using AuthStack tokens
  • Supports flexible response formats (AuthStack format or custom backend format)
  • Automatically stores tokens in configured token storage

Added #

• getProviderAuthUrl() method to get OAuth authorization URLs for providers (GitHub, Google, etc.)
  • Enables centralized OAuth flow where AuthStack handles OAuth app configuration
  • Supports custom state parameter for CSRF protection
• getProviderCredentials() method to retrieve OAuth credentials for linked providers
  • Get access tokens to make API calls to provider APIs (e.g., GitHub API)
  • Includes token expiration checking
• New models: ProviderAuthUrl and ProviderCredentials
• Support for all OAuth providers: Google, GitHub, Microsoft, Apple, Discord

Changed #

• Enhanced documentation for OAuth provider integration

Fixed #

• Fixed SDK constraint from >=3.8.1 to >=3.5.0 to support Flutter 3.27.0 (Dart 3.6.0)
• Downgraded flutter_lints from ^6.0.0 to ^5.0.0 for Dart 3.6.0 compatibility

Changed #

• Updated package metadata and documentation

Added #

• Initial release of Voo AuthStack Client SDK
• Email/password authentication support
• OAuth provider support (Google, GitHub, Microsoft, Apple, Discord)
• Automatic token refresh with configurable thresholds
• Secure token storage
• Provider account linking
• Clean architecture with domain, data, and presentation layers
• Dio-based HTTP client with interceptors
• Comprehensive error handling with typed exceptions