(Click here to find 2022 release notes)
2023-05 (Feb 3, 2023)
Release 2023-5 includes several security and observability improvements to the CoreWeave beta. None of the updates rolled out today will result in visible changes to the CoreWeave provider. Rather, this release significantly improves the internal observability systems prior to making this capability generally available to the public.
This includes improvements to our logging systems by making sure we’re logging everything necessary, as well as ensuring those logs are actionable. We've also added disk and infrastructure monitoring, as well improvements to our alerting system so that we can proactively identify and remediate issues before they impact the end user experience.
We anticipate at least one more CoreWeave-focused release in the next 1-3 weeks, after which we hope to be in a position to launch this capability out of beta.
2023-04 (Feb 2, 2023)
2023-4 is a smaller release focused on fixes for a handful of platform defects.
The primary change in this release is the removal of the old-style preview links that were deprecated in our last release. Now, all preview links can be revoked from your console account. For more information on this change, please see the notes for release 2023-3.
- Fixed an issue with model cleanup in our beta CoreWeave provider that would occasionally fail to clean up models if the provider configuration for the parent project was modified (i.e. changing a project from on-demand to dedicated).
- Implemented a partial fix to an issue some non-North American users were experiencing where in rare cases, a stream would unexpectedly terminate. This fix is in three parts, with this release delivering changes in the core platform, as well as the changes to our dedicated providers. We anticipate two subsequent releases in the coming weeks which should fully address the issue, one for our SDK, and another for our on-demand providers.
- Fixed a defect where in some cases, users would be routed to the an on-demand provider, even if a more optimal dedicated provider had free capacity.
- We also rolled out a handful of other fixes to internal systems and workflows that are used by are development and customer success teams in the creation and operation of PureWeb Reality. However, these changes only impact internal (PureWeb) users of the system.
2023-03 (Jan 16, 2023)
Today’s release is exclusively bug fixes and security improvements. However one of the security improvements introduces a deprecating change to the preview client. We sent out an email update about this change last week, but have included it below for completeness.
- Fixed an issue where console error messages would not be visible if your project contained several (~8+) models.
- Fixed the ‘Touch Events’ configuration setting in the ‘Share Model’ dialog. The dropdown menu previously did not include any options.
- Late last year we rolled out a new content security policy for the console and preview clients. This had the unintended consequence of preventing the preview client from being embedded in another website. This has been fixed, and the preview client should once again be embeddable.
- Updated the platform-cli to resolve an issue where passing the
--yesflag to bypass interactive prompts when uploading / creating a model, the
--exeflag would be ignored.
- Fixed an issue in the SDK where Unreal 5.1 models which employed ray tracing would fail to connect to a stream. This fix can be found in 3.23+ of the PureWeb platform SDK.
- Finally, this release introduces a new URL format for the preview client, which will also mean that the old format is deprecated and will be removed later this month. More on this change below.
Preview Client URL changes
Currently, if an anonymous preview link had been publicly disclosed, anyone can access that link in perpetuity. This presents security concerns, as it can lead to unexpected usage and consumption charges, and in the worst case, lead to denial of service attacks on your project.
The only way to prevent access to the project would be to take it offline, or turn off “Allow Unrestricted Access” access. Neither of these options are desirable if your intention is to continue using the preview client for public access, but you just want a better way of controlling that access. Based on feedback from our customers and guidance from our 3rd party security consultants, we’ve implemented a more secure mechanism for accessing preview links.
This release ensures that you can share your anonymous preview links, with the knowledge that you can revoke access to that link at any point in time, offering better control over who accesses your model.
What will be different with this change?
The current (soon-to-be-deprecated) pattern for preview links are of the form:
Where all of the IDs are static for the life of the given model version (version ID is optional).
The new pattern for preview links will be in the following form:
Where the version-ID is the same as it was before (still optional), but the secure hash will now resolve to your unique model and project. More importantly, you will be able to cycle the secure-hash at any point in time from the PureWeb console. This will invalidate any links that used the old hash, and provide you with a new link.
You can get this new hash URL either directly from the address bar of your browser in the preview client, or from the ‘Share’ menu in the model menu within your PureWeb Console account. This is also where you’ll be able to revoke and generate a new sharing URL. If you want to fully shut off public access, we still recommend disabling “Allow Unrestricted Access" in your project settings in the developer console.
This release will introduce the new URL mechanism as the default way of accessing the preview client. However, you’ll still be able to access your model via the old-style preview link for a minimum of two weeks.
On or after January 30th, we'll be removing the old URL pattern, at which point, only the new secure URL pattern will work.
What do you need to do?
If you have not shared preview links publicly, or embedded preview links in other websites, then you don’t have to do anything.
If you have embedded a static preview URL into another website, you’ll need to update that URL to a new dynamic hashed URL before January 30th.
Additionally, if you have shared an old-style static preview URL to colleagues, clients, or partners, you’ll have to send a new dynamic preview URL before January 30th.
If you access your model from a custom client, you do not need to make any changes, and your client and model access will not be affected.
2023-02 (Jan 5, 2023)
Release 2023-2 involved expanding our existing on-demand offering by adding a new server pool in Japan. We’re always keeping a close eye on system usage, and based on user activity, we’ve decided it was warranted to add an additional pool in the Asian region, to help meet user demand, and ensure an even better streaming experience for users in the region.
If you are already using our on-demand offering, no updates or configuration changes will be needed. If you have streaming users in Asia, they will automatically use this pool, if it is the best option for them in terms of network latency.
2023-01 (Jan 4, 2023)
Our first release of 2023 is a major update to our new CoreWeave on-demand beta provider type. As we get closer to the GA for this new capability, we are focused exclusively on security, stability, and performance improvements as well as integrating this new provider with our observability, health check, and eventing systems, so we can proactively monitor the system as it moves to production. This release delivers over a dozen fixes and improvements along these lines. For users of the system, you should generally see faster more consistent session launches with fewer errors. We've also further improved process and model security in the runtime environment. Finally, we've fixed a long standing defect in the beta that caused Unity games to max out at a resolution of 720p.
The last major push before the GA release of this capability is load and stress testing, which we’ll be focused on for the next few weeks. We’ll be addressing any defects or bottlenecks that we identify as part of this load testing, after which, we anticipate that we'll be in a position to make this capability available to all users by default.
Click here if you are looking for previous release notes.