Releases: mjsqu/pipelinewise-target-snowflake
v2.2.10
v2.2.9
Pinning certifi module to mitigate connection errors
How will this affect my service?
Customers hosted in AWS regions may encounter the error "The certificate is revoked or could not be validated" and are unable to use the Python and Spark connectors to perform specific operations that require an external AWS S3 stage with certificate check enabled. This issue primarily affects users who have recently upgraded the certifi library to version 2025.4.26.
What action do I need to take?
Potential temporary workarounds for customers with AWS EMR jobs may include the following:
Reverting to the previous certifi library version (2025.1.31) to restore the recently removed certificate trust. Customers can revert to the previous version using “pip install certifi==2025.1.31”
https://status.snowflake.com/incidents/txclg2cyzq32
Full Changelog: v2.2.8...v2.2.9
v2.2.8
What's Changed
- Migrate to pyproject.toml
- Update to allow keypair authentication using:
- private_key
- private_key_passphrase
Full Changelog: v2.2.7...v2.2.8
v2.2.7
2.2.6
2.2.5
Update to use snowflake-connector-python 3.5.0 which in turn updates the following upstream packages:
- pyarrow
- cryptography
to resolve security issues (CVE-2023-38325)
cryptography>=41.0.3
to resolve security issues 2023-11-25 (CVE-2023-47248)
pyarrow>=14.0.1
Updating to use snowflake 3.5.0 uplifts these packages to:
- cryptography>=3.1.0,<42.0.0
- pyarrow (no version specified - so latest - at the time of writing this is 14.0.1)
2.2.4
2.2.3
2.2.2
Update snowflake-connector-python[pandas] requirement from ==2.7.* to >=2.7,<3.1 (Dependabot Alert CVE ID: CVE-2022-42965)