Skip to content

Commit 73ea3f2

Browse files
committed
changeset cleanup
1 parent 159b79b commit 73ea3f2

1 file changed

Lines changed: 0 additions & 4 deletions

File tree

.changeset/async-resolve-config.md

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,7 @@
11
---
22
'@salesforce/b2c-tooling-sdk': minor
3-
'@salesforce/b2c-cli': patch
4-
'@salesforce/b2c-dx-mcp': patch
53
---
64

75
`resolveConfig()` and the `ConfigSource` interface are now async. This enables config sources that perform async I/O such as keychain lookups, credential vaults, or network-based config stores.
86

97
**Breaking:** `resolveConfig()` now returns `Promise<ResolvedB2CConfig>` — callers must `await` the result. The `ConfigSource.load()` method return type is now `MaybePromise<ConfigLoadResult | undefined>`, so existing sync source implementations continue to work without changes.
10-
11-
Built-in sources (`DwJsonSource`, `MobifySource`, `PackageJsonSource`) now use async `fs.promises` for non-blocking file I/O. `InstanceManager` methods and `ConfigSource` instance management methods (`listInstances`, `createInstance`, `removeInstance`, `setActiveInstance`, `storeCredential`, `removeCredential`) also accept async return values via `MaybePromise<T>`.

0 commit comments

Comments
 (0)