SNOW-3812183: v4.7.1 release notes claim pandas 3 support, but published wheel still requires pandas <3.0 #2953

Python version

Python 3.12.x, Python 3.13.x

Operating system and processor architecture

Windows 11 x64

Installed packages

snowflake-connector-python==4.7.1
pandas==3.0.3
pip==26.1.2
setuptools==78.1.1
wheel==0.45.1

What did you do?

Installed the Snowflake connector with the `pandas` extra while explicitly requesting pandas 3.0.3:
`pip install --upgrade "snowflake-connector-python[pandas]==4.7.1" "pandas==3.0.3"`
Pip reports a dependency resolution conflict because the published `v4.7.1` wheel still declares:
Requires-Dist: pandas<3.0.0,...
I noticed that the official Python Connector release notes for v4.7.1 state:
> Removed the pandas upper bound dependency constraint on the `[pandas]` extra to allow installation of pandas 3.0.0 and later.
However, the released package metadata still enforces `pandas<3.0.0`.
I have reproduced this with both Python 3.12 and Python 3.13.

What did you expect to see?

Installed the Snowflake connector with the pandas extra while explicitly requesting pandas 3.0.3:

pip install --upgrade "snowflake-connector-python[pandas]==4.7.1" "pandas==3.0.3"

Pip reports a dependency resolution conflict because the published v4.7.1 wheel still declares:

Requires-Dist: pandas<3.0.0,...

However, the official v4.7.1 release notes state:

Removed the pandas upper bound dependency constraint on the [pandas] extra to allow installation of pandas 3.0.0 and later.

Release notes: https://docs.snowflake.com/en/release-notes/clients-drivers/python-connector-2026

GitHub release: https://github.com/snowflakedb/snowflake-connector-python/releases/tag/v4.7.1

I have reproduced this on both Python 3.12 and Python 3.13.

Based on the release notes, I expected the connector to allow installation alongside pandas 3.x without a dependency conflict.

Instead, pip correctly refuses to resolve the dependencies because the published wheel still requires pandas<3.0.0.

Could you please clarify whether:

• the release notes are incorrect, or
• the published wheel metadata was not updated as intended?

If this is expected behavior, the release notes may need to be updated to avoid confusion.

Can you set logging to DEBUG and collect the logs?

This issue occurs during dependency resolution before the connector is installed or executed, so there are no connector DEBUG logs to collect. The failure is produced by pip due to the package metadata.