Skip to content

Release notes for SDK v0.27.0#2637

Open
mdlinville wants to merge 6 commits into
mainfrom
DOCS-2645
Open

Release notes for SDK v0.27.0#2637
mdlinville wants to merge 6 commits into
mainfrom
DOCS-2645

Conversation

@mdlinville
Copy link
Copy Markdown
Contributor

@mdlinville mdlinville commented May 15, 2026

Description

Release notes for SDK v0.27.0

Drafts worked out in https://weightsandbiases.slack.com/archives/C0108SLEP6K/p1778880117545879

Fixes DOCS-2645

Testing

  • Local build succeeds without errors (mint dev)
  • Local link check succeeds without errors (mint broken-links)
  • PR tests succeed

@mdlinville mdlinville requested a review from a team as a code owner May 15, 2026 21:55
@mintlify
Copy link
Copy Markdown
Contributor

mintlify Bot commented May 15, 2026

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
wandb 🟢 Ready View Preview May 15, 2026, 9:59 PM

@mdlinville mdlinville requested review from dmitryduev and timoffex May 15, 2026 21:55
Comment thread release-notes/sdk-releases.mdx
Comment thread release-notes/sdk-releases.mdx Outdated
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 15, 2026

📚 Mintlify Preview Links

🔗 View Full Preview

📝 Changed (1 total)

📄 Pages (1)

File Preview
release-notes/sdk-releases.mdx Sdk Releases

🤖 Generated automatically when Mintlify deployment succeeds
📍 Deployment: 18c5f05 at 2026-05-19 23:42:53 UTC

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 15, 2026

🔗 Link Checker Results

All links are valid!

No broken links were detected.

Checked against: https://wb-21fd5541-docs-2645.mintlify.app

Comment thread release-notes/sdk-releases.mdx Outdated
Comment thread release-notes/sdk-releases.mdx Outdated
Comment thread release-notes/sdk-releases.mdx Outdated
Comment thread release-notes/sdk-releases.mdx Outdated

## Added
- The new package `wandb.sandbox` package and the `wandb beta sandbox` CLI for using [Serverless Sandboxes](/sandboxes).
- The new setting `stop_on_fatal_error` stops a run after a fatal error that prevents it from uploading metrics.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

The WANDB_STOP_ON_FATAL_ERROR environment variable also works (this is true in general for all string or number settings, unlike stop_fn)

- The new package `wandb.sandbox` package and the `wandb beta sandbox` CLI for using [Serverless Sandboxes](/sandboxes).
- The new setting `stop_on_fatal_error` stops a run after a fatal error that prevents it from uploading metrics.
- The new setting `finish_timeout` and corresponding environment variable `WANDB_FINISH_TIMEOUT` let you specify how many seconds to wait for data to upload at the end of a run. If a run times out, a warning message is printed. Use boolean setting `finish_timeout_raises` or corresponding environment variable `WANDB_FINISH_TIMEOUT_RAISES` to raise an error in addition to printing a warning message.
- The new setting `capture_loggers` lets you control Python loggers to capture into the run's **Logs** tab, using a mapping of logger name to minimum log level. When set, `wandb` installs a `logging.Handler` on each named logger and removes it when the run finishes. Log records emitted by those loggers are published as console output to the run, similar to `stdout`/`stderr` capture.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

The wording of "lets you control Python loggers to capture" feels awkward to me. I'd say "specify" instead of "control".

The part about the logging.Handler is too detailed for the changelog - the setting can be used without knowing this. I put this in the setting's docs because it can still be important in niche situations.

Comment thread release-notes/sdk-releases.mdx Outdated
- The new setting `stop_on_fatal_error` stops a run after a fatal error that prevents it from uploading metrics.
- The new setting `finish_timeout` and corresponding environment variable `WANDB_FINISH_TIMEOUT` let you specify how many seconds to wait for data to upload at the end of a run. If a run times out, a warning message is printed. Use boolean setting `finish_timeout_raises` or corresponding environment variable `WANDB_FINISH_TIMEOUT_RAISES` to raise an error in addition to printing a warning message.
- The new setting `capture_loggers` lets you control Python loggers to capture into the run's **Logs** tab, using a mapping of logger name to minimum log level. When set, `wandb` installs a `logging.Handler` on each named logger and removes it when the run finishes. Log records emitted by those loggers are published as console output to the run, similar to `stdout`/`stderr` capture.
- The new method `run.write_logs()` writes text directly to the run's **Logs** tab instead of relying on automatic capture of `stdout`/`stderr`. Calls for a finished run are silently ignored.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

"Calls for a finished run are silently ignored" is also too much detail for the changelog.

Copy link
Copy Markdown
Member

@dmitryduev dmitryduev left a comment

Choose a reason for hiding this comment

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

approved modulo the remaining comments not to block :)

Comment thread release-notes/sdk-releases.mdx Outdated
- The new package `wandb.sandbox` package and the `wandb beta sandbox` CLI for using [Serverless Sandboxes](/sandboxes).
- The new setting `stop_on_fatal_error` stops a run after a fatal error that prevents it from uploading metrics.
- The new setting `finish_timeout` and corresponding environment variable `WANDB_FINISH_TIMEOUT` let you specify how many seconds to wait for data to upload at the end of a run. If a run times out, a warning message is printed. Use boolean setting `finish_timeout_raises` or corresponding environment variable `WANDB_FINISH_TIMEOUT_RAISES` to raise an error in addition to printing a warning message.
- The new setting `capture_loggers` lets you control Python loggers to capture into the run's **Logs** tab, using a mapping of logger name to minimum log level. When set, `wandb` installs a `logging.Handler` on each named logger and removes it when the run finishes. Log records emitted by those loggers are published as console output to the run, similar to `stdout`/`stderr` capture.
Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Suggested change
- The new setting `capture_loggers` lets you control Python loggers to capture into the run's **Logs** tab, using a mapping of logger name to minimum log level. When set, `wandb` installs a `logging.Handler` on each named logger and removes it when the run finishes. Log records emitted by those loggers are published as console output to the run, similar to `stdout`/`stderr` capture.
- The new setting `capture_loggers` lets you specify Python loggers to capture into the run's **Logs** tab, using a mapping of logger name to minimum log level. Log records emitted by those loggers are published as console output to the run, similar to `stdout`/`stderr` capture.

@timoffex WDYT?

Comment thread release-notes/sdk-releases.mdx Outdated
Co-authored-by: Timofey Peshin <timoffex@gmail.com>
Co-authored-by: Matt Linville <matt@linville.me>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants