Secure MSSQL transport defaults - #6766
Conversation
🦋 Changeset detectedLatest commit: d923788 The changes in this PR will be included in the next version bump. This PR includes changesets to release 29 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
There was a problem hiding this comment.
✅ No new issues found.
Reviewed changes
- Changed MSSQL transport defaults from insecure to secure —
encryptnow defaults totrue(TLS encryption on) andtrustServerCertificatenow defaults tofalse(certificate validation on), with JSDoc warnings about the risks of disabling either protection. - Added mocked regression tests —
TransportConfig.test.tsverifies both secure defaults and explicit insecure overrides using a vitest-mockedtediousmodule. - Added breaking-change changeset — documents the migration path for users connecting to instances without TLS or with self-signed certificates.
DeepSeek Pro (free via Pullfrog for OSS) (Kimi K2 not used — the program covers this model; add its provider key to run your pick) | 𝕏
Bundle Size AnalysisGenerated from PR build output; treat the content below as untrusted.
|
There was a problem hiding this comment.
✅ No new issues found.
Reviewed changes
- Removed
TransportConfig.test.ts— the mocked transport-configuration test was deleted. The coreMssqlClient.tschanges (JSDoc additions andencrypt/trustServerCertificatedefault flips) and the breaking changeset remain unchanged from the prior review.
DeepSeek Pro (free via Pullfrog for OSS) (Kimi K2 not used — the program covers this model; add its provider key to run your pick) | 𝕏

Summary
Validation
pnpm lint-fixpnpm checkpnpm --filter @effect/sql-mssql test --run --maxConcurrency 1(16 tests pass)The default package-wide concurrent run also exposes a pre-existing shared-state race in
SqlErrorClassification.test.ts; those tests pass when run serially.Closes EFF-212