refactor(coding-agent): move auth storage to backend abstraction
This commit is contained in:
@@ -5,10 +5,12 @@
|
||||
### Breaking Changes
|
||||
|
||||
- `SettingsManager` persistence semantics changed for SDK consumers. Setters now update in-memory state immediately and queue disk writes. Code that requires durable on-disk settings must call `await settingsManager.flush()`.
|
||||
- `AuthStorage` no longer uses direct constructor path convenience in SDK-facing usage. Use static factories (`AuthStorage.create(...)`, `AuthStorage.fromStorage(...)`, `AuthStorage.inMemory(...)`).
|
||||
|
||||
### Added
|
||||
|
||||
- Added `SettingsManager.drainErrors()` for caller-controlled settings I/O error handling without manager-side console output.
|
||||
- Added auth storage backends (`FileAuthStorageBackend`, `InMemoryAuthStorageBackend`) and `AuthStorage.fromStorage(...)` for storage-first auth persistence wiring.
|
||||
|
||||
### Changed
|
||||
|
||||
@@ -17,6 +19,8 @@
|
||||
### Fixed
|
||||
|
||||
- Fixed project settings persistence to preserve unrelated external edits via merge-on-write, while still applying in-memory changes for modified keys.
|
||||
- Fixed auth credential persistence to preserve unrelated external edits to `auth.json` via locked read/merge/write updates.
|
||||
- Fixed auth load/persist error surfacing by buffering errors and exposing them via `AuthStorage.drainErrors()`.
|
||||
|
||||
## [0.52.12] - 2026-02-13
|
||||
|
||||
|
||||
Reference in New Issue
Block a user