@@ -7,6 +7,42 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
7
7
8
8
## [ Unreleased]
9
9
10
+ ## [ 3.0.0] - 2025-07-17
11
+
12
+ ### 🔴 Breaking Changes
13
+ - ** Authentication System Overhaul** : Migrated from JWT to Better Auth session-based authentication
14
+ - ** Login Method Changed** : Users now log in with email instead of username
15
+ - ** Environment Variables** : ` JWT_SECRET ` renamed to ` BETTER_AUTH_SECRET ` , new ` BETTER_AUTH_URL ` required
16
+ - ** API Endpoints** : Authentication endpoints moved from ` /api/auth/login ` to ` /api/auth/[...all] `
17
+
18
+ ### Added
19
+ - ** Token Encryption** : All GitHub and Gitea tokens now encrypted with AES-256-GCM
20
+ - ** SSO/OIDC Support** : Enterprise authentication with OAuth providers (Google, Azure AD, Okta, Authentik, etc.)
21
+ - ** Header Authentication** : Support for reverse proxy authentication headers (Authentik, Authelia, Traefik Forward Auth)
22
+ - ** OAuth Provider** : Gitea Mirror can act as an OIDC provider for other applications
23
+ - ** Automated Migration** : Docker containers auto-migrate from v2 to v3
24
+ - ** Session Management** : Improved security with session-based authentication
25
+ - ** Database Migration System** : Drizzle Kit for better schema management
26
+ - ** Zod v4 Compatibility** : Updated to Zod v4 for schema validation
27
+
28
+ ### Improved
29
+ - ** Security** : Enhanced error handling and security practices throughout
30
+ - ** Documentation** : Comprehensive migration guide for v2 to v3 upgrade
31
+ - ** User Management** : Better Auth provides improved user lifecycle management
32
+ - ** Database Schema** : Optimized with proper indexes and relationships
33
+ - ** Password Hashing** : Using bcrypt via Better Auth for secure password storage
34
+
35
+ ### Fixed
36
+ - Mirroring issues for starred repositories
37
+ - Various security vulnerabilities in authentication system
38
+ - Improved error handling across all API endpoints
39
+
40
+ ### Migration Required
41
+ - All users must re-authenticate after upgrade
42
+ - Existing tokens will be automatically encrypted
43
+ - Database schema updates applied automatically
44
+ - See [ Migration Guide] ( MIGRATION_GUIDE.md ) for detailed instructions
45
+
10
46
## [ 2.22.0] - 2025-07-07
11
47
12
48
### Added
0 commit comments