. This brings our automated exports into parity with the Cloudsmith UI and manual CSV downloads, giving you deeper visibility into your package delivery performance.

For teams managing high-traffic repositories or optimizing CI/CD pipelines, understanding cache performance is vital. This update ensures your external logging and observability tools have the same level of granularity as the Cloudsmith web app.

 Identifies whether a package was served from an existing cache (

 This field is now live and included in the JSON payload. As a standard JSON addition, this is a non-breaking change for downstream consumers.

 To prevent breaking existing automated workflows, we are releasing the CSV update separately. We are currently coordinating with customers who utilize our larger CSV delivery format to ensure a smooth transition.

We’ve rolled out a suite of updates to 

 to help you deliver a more professional, secure, and transparent experience to your end users.

: Ultra and Enterprise customers can now remove Cloudsmith branding from their portal. Keep your brand front and center with a fully white-labeled interface.

 Docker tags are now visible directly within the package table and details page, providing full context at a glance for faster discovery.

 GPG fingerprint information is now displayed prominently, giving your users immediate confidence in the security and integrity of every package they install.

No more guessing with long version numbers

: Tooltips now display the full version string on hover, ensuring you can identify the exact package you need without confusion.

 are now generally available for all customers. If you're interested in distributing proprietary software securely, 

Recent improvements to Broadcasts

 offers a flexible way to upload and manage any file or binary within Cloudsmith. This release includes 

, enabling teams to fetch assets from external sources that don’t fit into standard package ecosystems.

This brings your custom scripts, installers, and zipped binaries into your managed supply chain, automating ingestion and ensuring that your internal URLs remain consistent with upstream sources.

The Generic format is designed for artifacts that rely on specific file paths rather than semantic versions. By using the filepath as the unique identifier, this format allows you to mirror the exact directory structures of external sources (like a raw Apache file server or a Gradle distribution) directly within Cloudsmith.

 Use filepaths as unique identifiers to replicate upstream directory structures exactly as they exist at the source.

Proxy & cache from upstream repositories:

 Securely fetch and cache files from external sources, creating a more secure and reliable internal supply chain.

 We merge local packages and cached upstream files into a single, browsable HTML index.

 Prevent file collisions between multiple upstreams by assigning unique path prefixes (e.g., gradle_distributions/) to keep assets distinct.

The Generic format connects to a wide variety of sources via three primary methods:

 Connects to any simple, unstyled HTML directory (no JavaScript) to index and download files. Works out-of-the-box for sources like 

 We offer specialized handlers for specific ecosystems, including 

 that use JavaScript rendering, we support integration via their APIs. 

Note: Due to the variability of these environments, these upstreams require a dedicated configuration. Please contact us to help set this up.

. You can begin using it today by creating a new repository and selecting "Generic" as the format type for upload.

 for additional instructions, and please 

 with any questions or feedback as we continue to refine the format.

Mirror external file structures and secure your binaries with the new Generic format

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.

You can now select up to 100 packages within a repository and apply common actions in a single step—such as copying packages, triggering a resync, quarantining content, and more. This helps teams maintain control and consistency across their repositories while reducing manual effort.

Perform bulk actions instead of repeating the same operation package by package.

Apply actions consistently across selected packages, lowering the chance of missed steps or configuration drift.

Whether you’re responding to a security issue, promoting artifacts, or cleaning up repositories, multi-select makes large-scale package management far more efficient.

 This release supports actions on up to 100 packages at a time. We plan to increase this capacity to 1,000 packages in early Q2.

 To ensure data safety, bulk deletion is currently disabled. It will be enabled alongside our upcoming 

 feature (scheduled for early Q2), ensuring you can recover accidentally deleted assets.

Multi-select package actions are now available on the web app

Last year, we launched Cloudsmith’s new documentation platform at 

. This refreshed and re-architected website - now powered by a “docs-as-code” workflow - offers more expansive content and simplified navigation, designed to reflect the speed and feel of the modern Cloudsmith web application.

Since that launch, we’ve been running our old documentation website alongside the new to ensure a smooth transition. It’s now time to formalize the sunsetting plan for our 

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 are committed to transparency throughout this process. The old docs site will remain available until the end of March 2026.

: While both sites remain live, no further content changes or updates will be made to the old documentation website.

: We will launch the API sandbox on the new documentation website, bringing full interactivity to our API docs.

: The old documentation website (help.cloudsmith.io) will be fully retired and decommissioned.

We are implementing 1:1 redirects for the majority of our documentation. If you click a link to an old 

 article, we will automatically route you to its updated home on 

If you notice any gaps in the new documentation or have feedback on how we can make your experience better, please 

. Better yet, the new site allows you to 

 - so if you see something that needs a fix, we’d welcome your contributions. We’d love to hear from you.

Timeline to sunset the old documentation site (help.cloudsmith.io)

We have updated the repository URL structure on the web app to disambiguate repositories from other static routes. This change applies only to the new web app.

app.cloudsmith.com/[WORKSPACE]/[REPOSITORY]/

app.cloudsmith.com/[WORKSPACE]/r/[REPOSITORY]/

We have set up redirects from the old path to the new one. This means if you have a bookmark to a repository, this link will automatically redirect you to the new URL.

New URL structure for repositories on the web app

Builds are now faster with support for parallel artifact uploads during 

Maven 3.9.12 enabled parallel deployment by default, which previously caused a race condition resulting in incomplete packages or synchronization errors. We updated our platform to support these concurrent requests, ensuring stability and reducing total build times.

This update is active for all customers using Maven 3.9.12 or later. No configuration changes are required.

New field: Cache hit / miss data added to client log exports

The details

Format & compatibility

Other logs

Recent improvements to Broadcasts

Mirror external file structures and secure your binaries with the new Generic format

Multi-select package actions are now available on the web app

Timeline to sunset the old documentation site (help.cloudsmith.io)

New URL structure for repositories on the web app

Support for Maven parallel deployment