deps(deps): bump pandas from 2.3.3 to 3.0.1 - #5011
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [pandas](https://github.com/pandas-dev/pandas) from 2.3.3 to 3.0.1. - [Release notes](https://github.com/pandas-dev/pandas/releases) - [Commits](pandas-dev/pandas@v2.3.3...v3.0.1) --- updated-dependencies: - dependency-name: pandas dependency-version: 3.0.1 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
🤖 Keepalive Loop StatusPR #5011 | Agent: Codex | Iteration 0/5 Current State
🔍 Failure Classification| Error type | infrastructure | |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: cbbff66c45
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| "numpy==2.4.2", | ||
| "openpyxl==3.1.5", | ||
| "pandas==2.3.3", | ||
| "pandas==3.0.1", |
There was a problem hiding this comment.
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 👍 / 👎.
|
Holding this Dependabot PR for manual review before merge: it is a major upgrade (pandas 2.x -> 3.x) and only updates . To avoid dependency drift/regression risk, this should merge together with explicit compatibility validation and any required pinned dependency file updates in the same branch. |
|
Holding this Dependabot PR for manual review before merge: it is a major upgrade (pandas 2.x -> 3.x) and only updates To avoid dependency drift/regression risk, merge this only with explicit compatibility validation and any required pinned dependency file updates in the same branch. |
|
Closing this pandas 3 Dependabot PR for now based on completed compatibility assessment from issue #5033. Assessment artifact:
Blocking findings from CI evidence:
Please re-open a pandas-3 upgrade PR after those blockers are addressed. |
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
Bumps pandas from 2.3.3 to 3.0.1.
Release notes
Sourced from pandas's releases.
... (truncated)
Commits
e04b26fRLS: 3.0.1 (#64206)47909e6[backport 3.0.x] ENH: Add item() method to ExtensionArray class (#64134) (#64...a061bfdBackport PR #64199 on branch 3.0.x (DOC: cleanup 3.0.1 whatsnew) (#64201)085a385[backport 3.0.x] BUG: Fix read_hdf failing on generic datetime64 dtype (#6400...5f17047[backport 3.0.x] BUG: use fill_null fallback for bug in pyarrow 21 on Windows...0d3a8cbBackport PR #64122 on branch 3.0.x (REG: Allow RE2 syntax in str.contains and...78e1917Backport PR #64185 on branch 3.0.x (TST: remove fixed xfail for PyArrow 23.0....75a42caBackport PR #64168 on branch 3.0.x (TST: add legacy file generation and tests...46d443fBackport PR #64092 on branch 3.0.x (BUG: DataFrame.loc fills b'' instead of N...9d67932Backport PR #64068 on branch 3.0.x (BUG: fixed to_timedelta with list of int ...Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)