BREAKING CHANGE(core): implement complete stateless architecture with consumer-controlled session persistence
This commit is contained in:
17
changelog.md
17
changelog.md
@@ -1,5 +1,22 @@
|
||||
# Changelog
|
||||
|
||||
## 2025-07-25 - 4.0.0 - BREAKING CHANGE(core)
|
||||
Complete stateless architecture - consumers now have full control over session persistence
|
||||
|
||||
- **BREAKING**: Removed all file-based persistence - no more automatic saving to .nogit/ directory
|
||||
- **BREAKING**: `init()` now returns `ISessionData` that must be persisted by the consumer
|
||||
- **BREAKING**: API methods like `getAccounts()` now return `{ data, sessionData? }` objects
|
||||
- Added `ISessionData` interface exposing complete session state including sessionId
|
||||
- Added `initWithSession(sessionData)` to initialize with previously saved sessions
|
||||
- Added `exportSession()` and `getSessionData()` methods for session access
|
||||
- Added `isSessionValid()` to check session validity
|
||||
- Fixed session destruction to use actual session ID instead of hardcoded '0'
|
||||
- Added `initOAuthWithExistingInstallation()` for explicit OAuth session handling
|
||||
- Session refresh now returns updated session data for consumer persistence
|
||||
- Added `example.stateless.ts` showing session management patterns
|
||||
|
||||
This change gives consumers full control over session persistence strategy (database, Redis, files, etc.) and makes the library suitable for serverless/microservices architectures.
|
||||
|
||||
## 2025-07-22 - 3.1.2 - fix(oauth)
|
||||
Remove OAuth session caching to prevent authentication issues
|
||||
|
||||
|
Reference in New Issue
Block a user