chore(deps): update dependency pandas to v2.3.3

[mergeraptor]

This PR contains the following updates:

Package	Change	Age	Confidence
pandas	==2.2.3 → ==2.3.3

---

Release Notes

pandas-dev/pandas (pandas)

v2.3.3: Pandas 2.3.3

Compare Source

We are pleased to announce the release of pandas 2.3.3.
This release includes some improvements and fixes to the future string data type (preview feature for the upcoming pandas 3.0). We recommend that all users upgrade to this version.

See the full whatsnew for a list of all the changes.
Pandas 2.3.3 supports Python 3.9 and higher, and is the first release to support Python 3.14.

The release will be available on the conda-forge channel:

conda install pandas --channel conda-forge

Or via PyPI:

python3 -m pip install --upgrade pandas

Please report any issues with the release on the pandas issue tracker.

Thanks to all the contributors who made this release possible.

v2.3.2: Pandas 2.3.2

Compare Source

We are pleased to announce the release of pandas 2.3.2.
This release includes some improvements and fixes to the future string data type (preview feature for the upcoming pandas 3.0). We recommend that all users upgrade to this version.

See the full whatsnew for a list of all the changes.
Pandas 2.3.2 supports Python 3.9 and higher.

The release will be available on the conda-forge channel:

conda install pandas --channel conda-forge

Or via PyPI:

python3 -m pip install --upgrade pandas

Please report any issues with the release on the pandas issue tracker.

Thanks to all the contributors who made this release possible.

v2.3.1: Pandas 2.3.1

Compare Source

We are pleased to announce the release of pandas 2.3.1.
This release includes some improvements and fixes to the future string data type (preview feature for the upcoming pandas 3.0). We recommend that all users upgrade to this version.

See the full whatsnew for a list of all the changes.
Pandas 2.3.1 supports Python 3.9 and higher.

The release will be available on the conda-forge channel:

conda install pandas --channel conda-forge

Or via PyPI:

python3 -m pip install --upgrade pandas

Please report any issues with the release on the pandas issue tracker.

Thanks to all the contributors who made this release possible.

v2.3.0: Pandas 2.3.0

Compare Source

We are pleased to announce the release of pandas 2.3.0.
This release includes some new features, bug fixes, and performance improvements. We recommend that all users upgrade to this version.

See the full whatsnew for a list of all the changes.
Pandas 2.3.0 supports Python 3.10 and higher.

The release will be available on the defaults and conda-forge channels:

conda install -c conda-forge pandas

Or via PyPI:

python3 -m pip install --upgrade pandas

Please report any issues with the release on the pandas issue tracker.

Thanks to all the contributors who made this release possible.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Never, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate.

[hanthor]

Review: Approved ✅

Standard dependency update.

[castrojo]

Lab run

Field	Value
Workflow	bluefin-qa-pipeline-zxqhd (Argo UI, logs)
Phase	Failed (infrastructure)
Duration	5m53s
Image / variant	ghcr.io/projectbluefin/bluefin:testing / bluefin
Suites	smoke
PR SHA	abdbcede0cfbe2a120306160f4b9ee0858fd3919

Result and diagnostics

Infrastructure / QA-runner failure; unrelated to this dependency-only diff. PR #261 changes only notebooks/requirements.txt (pandas==2.2.3 → 2.3.3). The workflow resolved and pulled the testing image at digest sha256:362d325d49631d57e59b314af04757790c696e17ee819f4b9fe5d155468f56a7, then the run-container-tests lane failed before test execution or result publication:

Nested systemd host did not reach a usable session state
systemd-resolved.service: Failed at step RUNTIME_DIRECTORY spawning /usr/lib/systemd/systemd-resolved: Read-only file system
Error: exit status 1

The pod was scheduled on Ready ghost; exo-0 and ghost were Ready during inspection. just list-vms showed no orphaned VMs (this is the container-only lane). No results.json / behave summary was produced.

This matches the existing infrastructure blocker projectbluefin/lab#297.

Queue action

No PR-branch fix or rerun was made: the failure is in the lab nested-systemd/session runner, not pandas. No lab-pass, approval, queue, or merge action taken. Rerun after #297 is repaired.