[dependabot]

Updates the requirements on wandb to permit the latest version.

Release notes

Sourced from wandb's releases.

v0.31.0

What's Changed

Notable Changes

• The default API endpoint is now CoreWeave Forge at https://api.forge.coreweave.com, and run links point to https://forge.coreweave.com/wandb. Existing API keys stored for api.wandb.ai keep working without logging in again.

Added

• Python 3.15 is now supported (@​dmitryduev in wandb/wandb#13167)
• wandb.init(resume="must") now works for offline runs. wandb sync fails if there is no run to resume (@​geoffhardy in wandb/wandb#12666)
• wandb sweep-scheduler [entity/project/]sweep_id runs a sweep's search locally with Optuna or Ax as the optimizer, configured in a scheduler block of the sweep config. wandb sweep prints the command for sweeps that set one (@​kmikowicz-wandb in wandb/wandb#12900)
• wandb agent --max-consecutive-failed-runs N shuts the agent down once N runs in a row have failed (@​nathancy-wandb in wandb/wandb#12821)
• wandb sync warns when a run was logged with a newer version of wandb than the one syncing it (@​timoffex in wandb/wandb#12808)
• W&B LEET TUI:
  • wandb leet inspect --summary prints a run's state, latest metric values, config and last console lines from its local .wandb file, a quick way for a script or a coding agent to check on a run. --json prints the records, or the summary, as JSON, and --follow keeps printing records as a running run writes them (@​dmitryduev in wandb/wandb#12951, wandb/wandb#12952)
  • l links the console logs to the charts in the single-run view: with the logs pane focused, the charts show a crosshair at the time the selected line was logged, and inspecting a chart with the mouse selects the console line logged nearest to that point. l again unlinks (@​dmitryduev in wandb/wandb#12737)
  • ctrl+a selects every run matching the runs filter, and x deselects all runs except the pinned one (@​dmitryduev in wandb/wandb#12904)
  • Selected and pinned runs are remembered per wandb directory and selected again the next time you open it. The newest run is selected as well if it started since the last session (@​dmitryduev in wandb/wandb#12887)
  • The CPU Core (%) chart opens as a heatmap with one row per core; y switches it back to lines (@​dmitryduev in wandb/wandb#13014)
• wandb leet symon, the live system monitor:
  • Shows the utilization of every CPU core, the CPU temperature and swap usage on Linux, and the hostname, uptime and load average in its header (@​dmitryduev in wandb/wandb#13012, wandb/wandb#13015)
  • Charts network and disk throughput in bytes per second instead of totals, and opens with the CPU, memory, network and disk charts ahead of the rest (@​dmitryduev in wandb/wandb#13013, wandb/wandb#13014)
  • Has a sidebar with the machine's chip, cores, memory and GPUs, live meters for CPU, memory, swap, disk and GPU use, and the processes using the most CPU. t sorts the processes by memory, f filters them by name or PID, Tab moves between the process list and the charts, and [ hides the sidebar. The sidebar can be resized by dragging its border, and 0 restores the default width (@​dmitryduev in wandb/wandb#13016, wandb/wandb#13017, wandb/wandb#13018, wandb/wandb#13021)
• New system metrics:
  • PCIe throughput (gpu.N.pcieTxBytes, gpu.N.pcieRxBytes) for NVIDIA GPUs older than Hopper (@​dmitryduev in wandb/wandb#12989)
  • Each GPU's cumulative energy consumption in joules as gpu.N.energyJoules, for NVIDIA and AMD GPUs (@​dmitryduev in wandb/wandb#12991)
  • proc.cpu.throttledPercent, the percentage of CPU scheduler periods in which the container's CPU limit throttled the run (@​dmitryduev in wandb/wandb#13001)
  • proc.memory.oomKills, how many processes in the run's container the out-of-memory killer has killed since the run started (@​dmitryduev in wandb/wandb#13002)
  • network.tcpRetransmits, the number of TCP segments retransmitted since the run started (@​dmitryduev in wandb/wandb#13003)
  • The CPU and memory used by W&B's own background processes, as wandb.cpu and wandb.memory.rssMB. They are off by default; turn them on with the x_stats_self_usage setting (@​dmitryduev in wandb/wandb#13004, wandb/wandb#13038)
• Run metadata now records the CPU model and, for each NVIDIA GPU, its PCI bus ID and, on Linux, its NUMA node (@​dmitryduev in wandb/wandb#13005, wandb/wandb#13157)

Changed

• The default W&B server is now CoreWeave Forge at https://api.forge.coreweave.com. Run, project, sweep and login links point to https://forge.coreweave.com/wandb, also when base_url is set to https://api.wandb.ai or https://forge.coreweave.com/api/wandb. Existing API keys stored for api.wandb.ai keep working without logging in again (@​dmitryduev in wandb/wandb#13077)
• The helper process that collects system metrics is now wandb-symon instead of wandb-xpu (@​dmitryduev in wandb/wandb#13165)
• import wandb and the wandb CLI start about twice as fast (@​dmitryduev in wandb/wandb#13144, wandb/wandb#13145, wandb/wandb#13146, wandb/wandb#13147, wandb/wandb#13148)
• The wandb package is smaller: wandb-core shrank by about a third, from 52 MB to 35 MB on Linux x86_64, and the parquet reader and the system metrics helper by more than half (@​dmitryduev in wandb/wandb#12921, wandb/wandb#12922, wandb/wandb#12923, wandb/wandb#12924, wandb/wandb#12937, wandb/wandb#12939)
• Runs write their data to the local .wandb file at least every 15 seconds, so wandb leet shows recent data sooner for runs that log infrequently (@​dmitryduev in wandb/wandb#12742)
• The cpu system metric reports the monitored process's CPU utilization over the sampling interval instead of its average since the process started (@​dmitryduev in wandb/wandb#13101)
• NVIDIA GPM system metrics such as gpu.N.smActive and gpu.N.dramActive are now averaged over the whole interval between samples instead of a 200 ms window (@​dmitryduev in wandb/wandb#12987)
• AMD GPU system metrics are read through the ROCm SMI library (librocm_smi64.so) instead of running the rocm-smi tool on every sample. Readings a GPU does not provide are left out instead of reported as 0 (@​dmitryduev in wandb/wandb#12990)
• OpenMetrics and DCGM exporter endpoints are scraped once per sampling interval for all runs on the machine instead of once per run, and all runs use the same openmetrics.<endpoint>.<metric>.<index> index for the same metric labels (@​dmitryduev in wandb/wandb#13103)

Removed

• Removed the undocumented wandb.set_trace(). Use Python's built-in breakpoint() instead (@​dmitryduev in wandb/wandb#12985)

Fixed

... (truncated)

Changelog

Sourced from wandb's changelog.

[0.31.0] - 2026-10-16

Notable Changes

• The default W&B server is now CoreWeave Forge at https://api.forge.coreweave.com, and run links point to https://forge.coreweave.com/wandb. Existing API keys stored for api.wandb.ai keep working without logging in again.

Added

• Python 3.15 is now supported (@​dmitryduev in wandb/wandb#13167)
• wandb.init(resume="must") now works for offline runs. wandb sync fails if there is no run to resume (@​geoffhardy in wandb/wandb#12666)
• wandb sweep-scheduler [entity/project/]sweep_id runs a sweep's search locally with Optuna or Ax as the optimizer, configured in a scheduler block of the sweep config. wandb sweep prints the command for sweeps that set one (@​kmikowicz-wandb in wandb/wandb#12900)
• wandb agent --max-consecutive-failed-runs N shuts the agent down once N runs in a row have failed (@​nathancy-wandb in wandb/wandb#12821)
• wandb sync warns when a run was logged with a newer version of wandb than the one syncing it (@​timoffex in wandb/wandb#12808)
• W&B LEET TUI:
  • wandb leet inspect --summary prints a run's state, latest metric values, config and last console lines from its local .wandb file, a quick way for a script or a coding agent to check on a run. --json prints the records, or the summary, as JSON, and --follow keeps printing records as a running run writes them (@​dmitryduev in wandb/wandb#12951, wandb/wandb#12952)
  • l links the console logs to the charts in the single-run view: with the logs pane focused, the charts show a crosshair at the time the selected line was logged, and inspecting a chart with the mouse selects the console line logged nearest to that point. l again unlinks (@​dmitryduev in wandb/wandb#12737)
  • ctrl+a selects every run matching the runs filter, and x deselects all runs except the pinned one (@​dmitryduev in wandb/wandb#12904)
  • Selected and pinned runs are remembered per wandb directory and selected again the next time you open it. The newest run is selected as well if it started since the last session (@​dmitryduev in wandb/wandb#12887)
  • The CPU Core (%) chart opens as a heatmap with one row per core; y switches it back to lines (@​dmitryduev in wandb/wandb#13014)
• wandb leet symon, the live system monitor:
  • Shows the utilization of every CPU core, the CPU temperature and swap usage on Linux, and the hostname, uptime and load average in its header (@​dmitryduev in wandb/wandb#13012, wandb/wandb#13015)
  • Charts network and disk throughput in bytes per second instead of totals, and opens with the CPU, memory, network and disk charts ahead of the rest (@​dmitryduev in wandb/wandb#13013, wandb/wandb#13014)
  • Has a sidebar with the machine's chip, cores, memory and GPUs, live meters for CPU, memory, swap, disk and GPU use, and the processes using the most CPU. t sorts the processes by memory, f filters them by name or PID, Tab moves between the process list and the charts, and [ hides the sidebar. The sidebar can be resized by dragging its border, and 0 restores the default width (@​dmitryduev in wandb/wandb#13016, wandb/wandb#13017, wandb/wandb#13018, wandb/wandb#13021)
• New system metrics:
  • PCIe throughput (gpu.N.pcieTxBytes, gpu.N.pcieRxBytes) for NVIDIA GPUs older than Hopper (@​dmitryduev in wandb/wandb#12989)
  • Each GPU's cumulative energy consumption in joules as gpu.N.energyJoules, for NVIDIA and AMD GPUs (@​dmitryduev in wandb/wandb#12991)
  • proc.cpu.throttledPercent, the percentage of CPU scheduler periods in which the container's CPU limit throttled the run (@​dmitryduev in wandb/wandb#13001)
  • proc.memory.oomKills, how many processes in the run's container the out-of-memory killer has killed since the run started (@​dmitryduev in wandb/wandb#13002)
  • network.tcpRetransmits, the number of TCP segments retransmitted since the run started (@​dmitryduev in wandb/wandb#13003)
  • The CPU and memory used by W&B's own background processes, as wandb.cpu and wandb.memory.rssMB. They are off by default; turn them on with the x_stats_self_usage setting (@​dmitryduev in wandb/wandb#13004, wandb/wandb#13038)
• Run metadata now records the CPU model and, for each NVIDIA GPU, its PCI bus ID and, on Linux, its NUMA node (@​dmitryduev in wandb/wandb#13005, wandb/wandb#13157)

Changed

• The default W&B server is now CoreWeave Forge at https://api.forge.coreweave.com. Run, project, sweep and login links point to https://forge.coreweave.com/wandb, also when base_url is set to https://api.wandb.ai or https://forge.coreweave.com/api/wandb. Existing API keys stored for api.wandb.ai keep working without logging in again (@​dmitryduev in wandb/wandb#13077)
• The helper process that collects system metrics is now wandb-symon instead of wandb-xpu (@​dmitryduev in wandb/wandb#13165)
• import wandb and the wandb CLI start about twice as fast (@​dmitryduev in wandb/wandb#13144, wandb/wandb#13145, wandb/wandb#13146, wandb/wandb#13147, wandb/wandb#13148)
• The wandb package is smaller: wandb-core shrank by about a third, from 52 MB to 35 MB on Linux x86_64, and the parquet reader and the system metrics helper by more than half (@​dmitryduev in wandb/wandb#12921, wandb/wandb#12922, wandb/wandb#12923, wandb/wandb#12924, wandb/wandb#12937, wandb/wandb#12939)
• Runs write their data to the local .wandb file at least every 15 seconds, so wandb leet shows recent data sooner for runs that log infrequently (@​dmitryduev in wandb/wandb#12742)
• The cpu system metric reports the monitored process's CPU utilization over the sampling interval instead of its average since the process started (@​dmitryduev in wandb/wandb#13101)
• NVIDIA GPM system metrics such as gpu.N.smActive and gpu.N.dramActive are now averaged over the whole interval between samples instead of a 200 ms window (@​dmitryduev in wandb/wandb#12987)
• AMD GPU system metrics are read through the ROCm SMI library (librocm_smi64.so) instead of running the rocm-smi tool on every sample. Readings a GPU does not provide are left out instead of reported as 0 (@​dmitryduev in wandb/wandb#12990)
• OpenMetrics and DCGM exporter endpoints are scraped once per sampling interval for all runs on the machine instead of once per run, and all runs use the same openmetrics.<endpoint>.<metric>.<index> index for the same metric labels (@​dmitryduev in wandb/wandb#13103)

Removed

• Removed the undocumented wandb.set_trace(). Use Python's built-in breakpoint() instead (@​dmitryduev in wandb/wandb#12985)

Fixed

... (truncated)

Commits

• 15f8cbc Bump version and update CHANGELOG for release 0.31.0
• 43f5b38 chore: clean up changelog for 0.31.0 release (#13182)
• e34448a chore(deps): update go dependencies (#13181)
• 6386f39 chore(deps): update github actions (version updates) (#13180)
• 445b90b chore(sdk): make the console log filestream writer tests order-independent (#...
• b279234 chore(sdk): let pytest see PROCESSOR_ARCHITECTURE on Windows (#13175)
• c74a4d1 chore(sdk): default EvalTable back to the Weave backend (#13172)
• 940d059 refactor(sdk): rename wandb-xpu to wandb-symon (#13165)
• 3294377 refactor(sdk): remove the system monitor's own sampling loop (#13158)
• ee63025 feat(sdk): read the host details wandb leet symon shows from wandb-xpu (#13157)
• Additional commits viewable in compare view

[dependabot]

Labels

The following labels could not be found: dependencies, python. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.