<#1084 fix: cap snowflake-connector-python &lt;5 i...
# flyte-github
a
#1084 fix: cap snowflake-connector-python <5 in snowflake plugin Pull request opened by pingsutw Summary • The connector image build in
.github/workflows/publish.yml
installs `flyteplugins-snowflake`/`-bigquery`/`-databricks` with
--pre
, which lets uv pick up the prerelease
snowflake-connector-python==5.0.0b1
(a Rust rewrite that needs
cargo
to build from source). The base connector image has no Rust toolchain, so the build fails with
FileNotFoundError: [Errno 2] No such file or directory: 'cargo'
. • This has broken the last three publish runs (v2.3.0, v2.3.1, v2.3.2) at the connector image step. Failing job: https://github.com/flyteorg/flyte-sdk/actions/runs/25925272795/job/76206538880 • Fix: cap
snowflake-connector-python[pandas]<5
in
plugins/snowflake/pyproject.toml
.
--pre
still resolves the flyteplugins prereleases, but uv honors the upper bound and picks the latest 4.x for snowflake-connector-python. • Regenerated
plugins/snowflake/uv.lock
. Note: the fix only takes effect once a new
flyteplugins-snowflake
wheel is published from this repo (the bound is baked into the wheel's metadata). A new release tag will be needed after merge. Test plan •
uv pip compile --pre
with the new constraint resolves to
snowflake-connector-python==4.5.0
locally. •
uv lock
succeeds in
plugins/snowflake/
with no other drift. • After merge + new release tag, confirm the
Build and push the connector image
step succeeds for all Python versions. flyteorg/flyte-sdk