Skip to content

Commit 66e8d45

Browse files
mdlinvillemdlinville
authored
Release notes for Server v0.82.0 (#2793)
1 parent fc30dc6 commit 66e8d45

2 files changed

Lines changed: 108 additions & 62 deletions

File tree

‎release-notes/server-releases-archived.mdx‎

Lines changed: 62 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -15,6 +15,68 @@ This page includes release notes for W&B Server releases that have reached end o
1515
{/* To archive a release, move its <Update> entries (including patches)
1616
from server-releases.mdx to just below here */}
1717

18+
<Update label="v0.70.1" description="July 9, 2025">
19+
## Fixes
20+
- Fixed a bug where the status of crashed runs was not updated to **Crashed** after an upgrade.
21+
- Fixed a bug where the **State** column was missing from the **Sweeps** Runs table.
22+
- Fixed a Weave bug where the browser for a Registry collection could display files from an incorrect version because the cached path for an artifact manifest file depended only on the artifact's version index.
23+
- Fixed a Weave bug that could prevent JSON with valid syntax from being parsed correctly.
24+
25+
These bugs were introduced in v0.70.0.
26+
</Update>
27+
28+
<Update label="v0.70.0" description="July 7, 2025">
29+
W&B Server v0.70 includes features, enhancements, and performance improvements to help you gain and share insights more efficiently. For example:
30+
31+
## Support and end of life
32+
- W&B Server v0.56 has reached end of life.
33+
34+
## Upcoming changes
35+
- In an upcoming release, we will align multi-run and single-run workspace views, so when you drill into a single run, you’ll see the same layout and configuration of panels as you’ve configured for the multi-run view, including any custom charts, layouts, and settings. The goal is help you stay in context and avoid re-work around configuring your views. However, this will remove the ability to customize unique single-run views, isolated from the rest of the workspace. Reach out to your W&B team or [support](mailto:support@wandb.ai) for any questions about the migration.
36+
- Over the next several releases, we will migrate existing team-level Model Registry W&B Registry. For details and a timeline, see the [W&B Registry GA announcement](#registry_ga_announcement) below.
37+
38+
## Features
39+
- <a id="registry_ga_announcement" aria-label="W&B Registry GA announcement"></a> **W&B Registry is now generally available**! Registry offers improved asset diversity, access management, and scalability, making it a true hub for collaborating on AI initiatives across large, diverse teams.
40+
- Registry can be turned on today with the `ENABLE_REGISTRY_UI` environment variable or by contacting your W&B support team.
41+
- We’re migrating existing team-level Model Registry assets to W&B Registry in stages over the next several releases. **No action is needed on your end. W&B will automatically copy Model Registry assets for each team to a corresponding automatically-created team-level private registry.**  Existing references to model collections in your old team-level Model Registry will still work.
42+
1. In Server v0.71, Registry will be on by default for all organizations.
43+
1. Server v0.73 (August) will contain an opt-out environment variable that will execute this migration automatically during the upgrade. Migration takes between 5 and 30 minutes for most organizations. During the migration, linking artifacts to either the old team’s Model Registry or the new Registry will fail with an error. ****Artifact logging and retrieval** **will not be affected**.
44+
1. In Server v0.74 (September), we will remove this flag and migration will happen during the upgrade.
45+
46+
We’re optimizing for a seamless, minimally-inconveniencing upgrade to a powerful new experience. Reach out to your W&B team or [support](mailto:support@wandb.ai) for any questions about the migration.
47+
- **CoreWeave infrastructure monitoring**: During a [W&B Run](/models/runs) on CoreWeave infrastructure, [CoreWeave Mission Control](https://www.coreweave.com/mission-control) monitors your compute infrastructure, allowing for observation of infrastructure alerts such as GPU failures, thermal violations, and more. If an error occurs, CoreWeave sends that information to W&B. W&B populates infrastructure information onto your run's plots in your project's workspace. CoreWeave attempts to resolve some issues automatically, and W&B surfaces that information in the run's page. W&B provides a link to the SLURM job's Grafana dashboard for system-level details about the run. Learn more at [Visualize CoreWeave infrastructure alerts](/models/app/features/panels/line-plot).
48+
- **CoreWeave external file tracking**: You can now track external files stored in CoreWeave AI Object Storage with reference artifacts. Learn more at [Track external files](/models/artifacts/track-external-files).
49+
- **CoreWeave BYOB support**: Dedicated Cloud and Self-Managed now support CoreWeave AI Object Storage for Instance and Team level BYOB. CoreWeave Team level BYOB on Multi-tenant Cloud is coming soon. Learn more at [Bring your own bucket (BYOB)](/platform/hosting/data-security/secure-storage-connector).
50+
- **Bulk media settings**: Just like line plots, you can now manage all your media panel settings at once—across an entire workspace or a specific section. Easily configure media panels to display by epoch or arrange them into customized grid patterns without adjusting each panel separately. Individual panel settings override the global settings.
51+
- Use **Workspace templates** to quickly create workspaces using the same settings as an existing workspace. Currently, a workspace template can define custom line plot settings. Learn more at [Workspace templates](/models/track/workspaces/#workspace-templates).
52+
- With **incremental table logging**, you can log batches of rows to a table during a machine learning experiment. This is ideal for monitoring long-running jobs or when working with large tables that would be inefficient to log during the run for updates. Within the UI, the table is updated with new rows as they are logged, so you can view the latest data without having to wait for the entire run to finish. You can step through the increments to view the table at different points in time. Learn more at [Log tables](/models/track/log/log-tables/#adding-data-incrementally).
53+
54+
## Fixes
55+
- Added a banner at the top of the log viewer if only a subset of lines is shown.
56+
- Fixed a bug in the running average calculation at data boundaries.
57+
- Clarified x-axis unit labels for relative time plots.
58+
- Fixed a bug in plots with smoothing where the original line would still display when **Show Original** was unchecked.
59+
- Fixed a bug that could unexpectedly convert a grouped full-fidelity line plot with expressions into a bar chart.
60+
- Hovering on histograms now shows the x-axis step in a tooltip.
61+
- Fixed a bug where data exported from a panel could sort incorrectly. Exported data now sorts numerically.
62+
- In the run selector, you can now filter and sort on **updated at**.
63+
- Added right-handed system setting option to point cloud panels.
64+
- Trailing slashes are now stripped from full screen panel URLs.
65+
- Fixed a bug where a deleted saved view could reappear if you refreshed immediately after deleting it.
66+
- Fixed a display bug that caused a flash when reloading a page with dark mode turned on.
67+
- Fixed a bug that caused incorrect slider steps when using non-monotonic values.
68+
- Added a convenience checkbox and notification when moving runs between groups.
69+
- Fixed a bug where using the wildcard character `*` for the metric name in `wandb.define_metric()` would fail to match metrics with `/` in the name.
70+
- W&B now no longer deletes source artifacts when collection portfolios are garbage collected.
71+
- Fixed a bug that incorrectly allowed typing input in **Allowed types** and **Registry visibility** selection boxes.
72+
- Collection cards now display the full artifact type name instead of truncating it.
73+
- Fixed a bug where clicking **Action History** in a Registry collection would incorrectly load the **Versions** view.
74+
- Registry now supports adding `job` type artifacts.
75+
- Lineage tiles are now wider, displaying more text before truncating.
76+
- Clarified text in project-level automation setup to refer to "artifacts" instead of the Registry terminology "collections".
77+
- The artifact browser now searches all artifacts when searching the artifact browser by name, rather than the previous limit of the first 500 artifacts.
78+
</Update>
79+
1880
<Update label="v0.69.1" description="June 10, 2025">
1981
## Fixes
2082
- You can now set the initial run state when creating a run with `Run.create()` by setting the `state` parameter to `pending` or `running`.

‎release-notes/server-releases.mdx‎

Lines changed: 46 additions & 62 deletions
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,52 @@ This page includes release notes for supported releases of W&B Server.
1212

1313
<EolReminder/>
1414

15+
<Update label="v0.82.0" description="June 23, 2026">
16+
**June 23, 2026**
17+
18+
W&B 0.82.0 brings richer artifact insights with editable collection overviews and version-level metric charts, along with workspace and run table quality-of-life improvements. To support enterprise administration, you can now assign Models seats and Weave roles when inviting members, and audit logs capture API key activity.
19+
20+
## Support and end of life
21+
22+
- W&B v0.70 has reached end of life.
23+
24+
## Features
25+
26+
- Pin and compare runs from different projects, or specify a run in a different project as the baseline run. See [Compare runs across projects](/models/runs/compare-runs#compare-runs-across-projects).
27+
<Frame>
28+
![Runs table with pinned runs from another project](/images/runs/compare_runs_ui_element.png)
29+
</Frame>
30+
- The W&B UI now shows the latest available W&B SDK version, so you can tell when a newer release is available.
31+
- Workspace browser tabs now include the active view name in the page title, making it easier to differentiate saved views across browser tabs.
32+
33+
### Registry
34+
35+
- The Registry **Advanced** search tab lets you efficiently search and filter registries, collections, and versions. Quickly search by object name, and filter objects by name, tags, created or updated date, parent registry, and more. Search performance and efficiency have been improved. See [Find registry items](/models/registry/search_registry).
36+
37+
### Weave
38+
39+
- The Weave LLM proxy now reports cost split into input and output token components, for finer-grained cost analysis.
40+
41+
## Security
42+
43+
- [Audit logs](/platform/hosting/monitoring-usage/audit-logging) now include API key information for relevant events.
44+
- Upgraded Redis to 8.6.3 to resolve the following CVEs:
45+
- [CVE-2026-25243](https://www.cve.org/CVERecord?id=CVE-2026-25243)
46+
- [CVE-2026-23631](https://www.cve.org/CVERecord?id=CVE-2026-23631)
47+
- [CVE-2026-23479](https://www.cve.org/CVERecord?id=CVE-2026-23479)
48+
49+
## Performance improvements
50+
51+
- Improved the efficiency of workspace panel search.
52+
53+
## Fixes
54+
55+
- Fixed an infinite loop in line plot panels with linear axes.
56+
- Fixed a bug when viewing a logged video in dark mode, where switching to full screen would show the video with light mode colors.
57+
- Fixed a bug where Weave panels in a workspace could lose their applied filters during auto-refresh.
58+
59+
</Update>
60+
1561
<Update label="v0.81.3" description="June 9, 2026">
1662
## Fixes
1763
- Removed an unsupported internal API endpoint.
@@ -861,65 +907,3 @@ With W&B Server 0.71, Registry is turned on by default for all organizations. Fo
861907
- Fixed wrapping of long names for Sweeps and Reports.
862908
- Improved the copy and paste behavior for console logs. Line numbers are no longer copied, and timestamps now appear inline instead of on a new line.
863909
</Update>
864-
865-
<Update label="v0.70.1" description="July 9, 2025">
866-
## Fixes
867-
- Fixed a bug where the status of crashed runs was not updated to **Crashed** after an upgrade.
868-
- Fixed a bug where the **State** column was missing from the **Sweeps** Runs table.
869-
- Fixed a Weave bug where the browser for a Registry collection could display files from an incorrect version because the cached path for an artifact manifest file depended only on the artifact's version index.
870-
- Fixed a Weave bug that could prevent JSON with valid syntax from being parsed correctly.
871-
872-
These bugs were introduced in v0.70.0.
873-
</Update>
874-
875-
<Update label="v0.70.0" description="July 7, 2025">
876-
W&B Server v0.70 includes features, enhancements, and performance improvements to help you gain and share insights more efficiently. For example:
877-
878-
## Support and end of life
879-
- W&B Server v0.56 has reached end of life.
880-
881-
## Upcoming changes
882-
- In an upcoming release, we will align multi-run and single-run workspace views, so when you drill into a single run, you’ll see the same layout and configuration of panels as you’ve configured for the multi-run view, including any custom charts, layouts, and settings. The goal is help you stay in context and avoid re-work around configuring your views. However, this will remove the ability to customize unique single-run views, isolated from the rest of the workspace. Reach out to your W&B team or [support](mailto:support@wandb.ai) for any questions about the migration.
883-
- Over the next several releases, we will migrate existing team-level Model Registry W&B Registry. For details and a timeline, see the [W&B Registry GA announcement](#registry_ga_announcement) below.
884-
885-
## Features
886-
- <a id="registry_ga_announcement" aria-label="W&B Registry GA announcement"></a> **W&B Registry is now generally available**! Registry offers improved asset diversity, access management, and scalability, making it a true hub for collaborating on AI initiatives across large, diverse teams.
887-
- Registry can be turned on today with the `ENABLE_REGISTRY_UI` environment variable or by contacting your W&B support team.
888-
- We’re migrating existing team-level Model Registry assets to W&B Registry in stages over the next several releases. **No action is needed on your end. W&B will automatically copy Model Registry assets for each team to a corresponding automatically-created team-level private registry.**  Existing references to model collections in your old team-level Model Registry will still work.
889-
1. In Server v0.71, Registry will be on by default for all organizations.
890-
1. Server v0.73 (August) will contain an opt-out environment variable that will execute this migration automatically during the upgrade. Migration takes between 5 and 30 minutes for most organizations. During the migration, linking artifacts to either the old team’s Model Registry or the new Registry will fail with an error. ****Artifact logging and retrieval** **will not be affected**.
891-
1. In Server v0.74 (September), we will remove this flag and migration will happen during the upgrade.
892-
893-
We’re optimizing for a seamless, minimally-inconveniencing upgrade to a powerful new experience. Reach out to your W&B team or [support](mailto:support@wandb.ai) for any questions about the migration.
894-
- **CoreWeave infrastructure monitoring**: During a [W&B Run](/models/runs) on CoreWeave infrastructure, [CoreWeave Mission Control](https://www.coreweave.com/mission-control) monitors your compute infrastructure, allowing for observation of infrastructure alerts such as GPU failures, thermal violations, and more. If an error occurs, CoreWeave sends that information to W&B. W&B populates infrastructure information onto your run's plots in your project's workspace. CoreWeave attempts to resolve some issues automatically, and W&B surfaces that information in the run's page. W&B provides a link to the SLURM job's Grafana dashboard for system-level details about the run. Learn more at [Visualize CoreWeave infrastructure alerts](/models/app/features/panels/line-plot).
895-
- **CoreWeave external file tracking**: You can now track external files stored in CoreWeave AI Object Storage with reference artifacts. Learn more at [Track external files](/models/artifacts/track-external-files).
896-
- **CoreWeave BYOB support**: Dedicated Cloud and Self-Managed now support CoreWeave AI Object Storage for Instance and Team level BYOB. CoreWeave Team level BYOB on Multi-tenant Cloud is coming soon. Learn more at [Bring your own bucket (BYOB)](/platform/hosting/data-security/secure-storage-connector).
897-
- **Bulk media settings**: Just like line plots, you can now manage all your media panel settings at once—across an entire workspace or a specific section. Easily configure media panels to display by epoch or arrange them into customized grid patterns without adjusting each panel separately. Individual panel settings override the global settings.
898-
- Use **Workspace templates** to quickly create workspaces using the same settings as an existing workspace. Currently, a workspace template can define custom line plot settings. Learn more at [Workspace templates](/models/track/workspaces/#workspace-templates).
899-
- With **incremental table logging**, you can log batches of rows to a table during a machine learning experiment. This is ideal for monitoring long-running jobs or when working with large tables that would be inefficient to log during the run for updates. Within the UI, the table is updated with new rows as they are logged, so you can view the latest data without having to wait for the entire run to finish. You can step through the increments to view the table at different points in time. Learn more at [Log tables](/models/track/log/log-tables/#adding-data-incrementally).
900-
901-
## Fixes
902-
- Added a banner at the top of the log viewer if only a subset of lines is shown.
903-
- Fixed a bug in the running average calculation at data boundaries.
904-
- Clarified x-axis unit labels for relative time plots.
905-
- Fixed a bug in plots with smoothing where the original line would still display when **Show Original** was unchecked.
906-
- Fixed a bug that could unexpectedly convert a grouped full-fidelity line plot with expressions into a bar chart.
907-
- Hovering on histograms now shows the x-axis step in a tooltip.
908-
- Fixed a bug where data exported from a panel could sort incorrectly. Exported data now sorts numerically.
909-
- In the run selector, you can now filter and sort on **updated at**.
910-
- Added right-handed system setting option to point cloud panels.
911-
- Trailing slashes are now stripped from full screen panel URLs.
912-
- Fixed a bug where a deleted saved view could reappear if you refreshed immediately after deleting it.
913-
- Fixed a display bug that caused a flash when reloading a page with dark mode turned on.
914-
- Fixed a bug that caused incorrect slider steps when using non-monotonic values.
915-
- Added a convenience checkbox and notification when moving runs between groups.
916-
- Fixed a bug where using the wildcard character `*` for the metric name in `wandb.define_metric()` would fail to match metrics with `/` in the name.
917-
- W&B now no longer deletes source artifacts when collection portfolios are garbage collected.
918-
- Fixed a bug that incorrectly allowed typing input in **Allowed types** and **Registry visibility** selection boxes.
919-
- Collection cards now display the full artifact type name instead of truncating it.
920-
- Fixed a bug where clicking **Action History** in a Registry collection would incorrectly load the **Versions** view.
921-
- Registry now supports adding `job` type artifacts.
922-
- Lineage tiles are now wider, displaying more text before truncating.
923-
- Clarified text in project-level automation setup to refer to "artifacts" instead of the Registry terminology "collections".
924-
- The artifact browser now searches all artifacts when searching the artifact browser by name, rather than the previous limit of the first 500 artifacts.
925-
</Update>

0 commit comments

Comments
 (0)