New field: Cache hit / miss data added to client log exports
We have added the edge_response field to our automated S3 and Azure client log exports…
We are deprecating the Client Logs, Client Statistics, and Package Statistics views within the classic Cloudsmith web app. Users navigating to these pages will now see a notice directing them to our new web application to view their data.
Why this change? To provide a faster, more reliable experience, we are sunsetting legacy infrastructure that is no longer receiving live updates. By retiring these dormant datasets and the underlying databases, we can reduce platform complexity and focus our resources on the high-speed data pipelines in the new web application.
Who is impacted? This affects all users of the classic web app. Instead of an empty table, you will see a direct link to your logs in the new interface.
What happens to my data?
If you have any questions or need help finding a specific view in the new app, contact us. We’re happy to help!
We have added the edge_response field to our automated S3 and Azure client log exports…
We’ve rolled out a suite of updates to Broadcasts to help you deliver a more professional, secure, and transparent experience to your end users…
Cloudsmith’s new Generic package format offers a flexible way to upload and manage any file or binary within Cloudsmith. This release includes upstream proxying and caching, enabling teams to fetch assets from external sources that don’t fit into standard package ecosystems…
We’ve added multi-select support for packages in the Cloudsmith web app, making it easier and faster to take action across multiple packages at once…
It's time to formalize the sunsetting plan for our old documentation website (help.cloudsmith.io). Maintaining a single, modern documentation platform helps Cloudsmith ensure technical accuracy, deliver updates faster, and invest in a great user experience for documentation across our platform…
We have updated the URL structure on the web app. This change will affect only the repository URLs and applies only to the new web app. The reason for this is to disambiguate repository URLs from other static routes…