Skip to content

deps(deps): bump pandas from 2.3.3 to 3.0.1 #5011

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
dependabot wants to merge 1 commit into from
Closed

deps(deps): bump pandas from 2.3.3 to 3.0.1 #5011

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion pyproject.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,7 +36,7 @@ dependencies = [
"matplotlib==3.10.8",
"numpy==2.4.2",
"openpyxl==3.1.5",
"pandas==2.3.3",
"pandas==3.0.1",

@chatgpt-codex-connector chatgpt-codex-connector Bot Feb 23, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Regenerate requirements.lock for pandas upgrade

After this change, pyproject.toml requires pandas==3.0.1, but requirements.lock still pins pandas==2.3.3 (line 297), so any workflow/script that installs via uv pip sync requirements.lock (for example scripts/setup_env.sh and scripts/run_tests.sh) will continue running on 2.3.3 and never actually pick up the 3.0.1 upgrade. That creates inconsistent environments and defeats the dependency bump in reproducible/test paths until the lockfile is regenerated.

Useful? React with 👍 / 👎.

"pandera==0.29.0",
"plotly==6.5.2",
"pydantic==2.12.5",
Expand Down
Loading