We added a JourneyServerConfig type import and narrowed serverConfig with as JourneyServerConfig at the three failing assertion sites. This resolves the TypeScript errors caused by the PR's change from toHaveProperty('wellknown', ...) to direct .wellknown access, which TypeScript checks against the declared union type JourneyServerConfig | LegacyServerConfig. The cast is safe because buildJourneyConfig always produces a JourneyServerConfig at runtime.
This code change can't be applied
A fix is available, but it can't be applied automatically because the branch is outdated. Please sync the branch, then apply the fix locally below.
Self-Healing CI
Classification: Code change needed
Fix generated
Verified 1 task
Commit"fix(sdk-utilities): narrow serverConfig type in wellknown assertions"
1 file changed
+4/−3