Describe the bug
As of February 1st, 2026 the snowflake-sdk driver version used in Evidence is not supported by Snowflake anymore, see here: https://docs.snowflake.com/en/release-notes/requirements
I tried updating it locally using overrides with the latest evidence and core-components but there's some hiccup in the connection. I'm not a JS expert, but Claude says something along the lines of "The error typically means we're trying to execute something before the connection is fully established, yet auth succeeded."
The actual error that happens with a version like 1.15.0 is pasted below.
Steps to Reproduce
- Add
"snowflake-sdk": "1.15.0" as override
- run
npm run sources with a Snowflake source using private key auth
Logs
[Processing] snowflake
{"level":"INFO","message":"[11:25:48.908 AM]: Creating new connection object"}
<some sensitive info removed>
{"level":"INFO","message":"[11:25:48.943 AM]: Connection[id: 21c05385-ec38-4eda-91fb-83e2dfe2ebdb] - connection object created successfully."}
{"level":"INFO","message":"[11:25:48.943 AM]: Connection[id: 21c05385-ec38-4eda-91fb-83e2dfe2ebdb] - connecting. Associated Snowflake domain: GLOBAL"}
{"level":"INFO","message":"[11:25:48.947 AM]: Connection[id: 21c05385-ec38-4eda-91fb-83e2dfe2ebdb] - authentication successful using: SNOWFLAKE_JWT"}
{"level":"INFO","message":"[11:25:48.947 AM]: Trying to initialize Easy Logging"}
[ ! ] Error connecting to datasource snowflake: Unable to perform operation because a connection was never established.
System Info
Not relevant
Severity
security issue
Additional Information, or Workarounds
None so far
Describe the bug
As of February 1st, 2026 the
snowflake-sdkdriver version used in Evidence is not supported by Snowflake anymore, see here: https://docs.snowflake.com/en/release-notes/requirementsI tried updating it locally using overrides with the latest
evidenceandcore-componentsbut there's some hiccup in the connection. I'm not a JS expert, but Claude says something along the lines of "The error typically means we're trying to execute something before the connection is fully established, yet auth succeeded."The actual error that happens with a version like 1.15.0 is pasted below.
Steps to Reproduce
"snowflake-sdk": "1.15.0"as overridenpm run sourceswith a Snowflake source using private key authLogs
[Processing] snowflake {"level":"INFO","message":"[11:25:48.908 AM]: Creating new connection object"} <some sensitive info removed> {"level":"INFO","message":"[11:25:48.943 AM]: Connection[id: 21c05385-ec38-4eda-91fb-83e2dfe2ebdb] - connection object created successfully."} {"level":"INFO","message":"[11:25:48.943 AM]: Connection[id: 21c05385-ec38-4eda-91fb-83e2dfe2ebdb] - connecting. Associated Snowflake domain: GLOBAL"} {"level":"INFO","message":"[11:25:48.947 AM]: Connection[id: 21c05385-ec38-4eda-91fb-83e2dfe2ebdb] - authentication successful using: SNOWFLAKE_JWT"} {"level":"INFO","message":"[11:25:48.947 AM]: Trying to initialize Easy Logging"} [ ! ] Error connecting to datasource snowflake: Unable to perform operation because a connection was never established.System Info
Not relevant
Severity
security issue
Additional Information, or Workarounds
None so far