Cloudsmith has always retained deleted packages for 7 days before permanently removing them — but until now, restoring a deleted package required contacting Cloudsmith support. The new “Recently deleted packages” view lets your team find and restore packages directly, whether they were removed manually, by a retention rule, or via a bulk action, without raising a support request.

From the recently deleted packages view, you can:

 across your entire workspace or scoped to a specific repository.

 that was deleted within the last 7 days.

 immediately, without waiting for the window to expire.

 has also been extended to support recently deleted packages and restore functionality.

The recently deleted packages view is available now in the Cloudsmith web app. Head to your workspace or repository to get started, or see the 

Cloudsmith should adapt to the way you work, and today we're releasing a significant new feature to meet this objective - 

With this release, you can now control which columns appear in many tables across our web application. You can also adjust the order of columns. We've also added an option to change table density, so you can fit more data on screen at once.

These new settings are available from dropdowns in column headers, or from a dedicated button above tables. Your choices are saved per table, so you'll always see your preferred view.

We're rolling out table personalization carefully - starting with packages, members, and services. More tables are coming soon.

Make Cloudsmith yours with personalized tables

We've made a series of usability improvements to 

If you haven't yet configured an upstream on a repository, a new streamlined setup makes it easy to connect to one in a single click.

An error tag is now displayed in the table if an upstream encounters a problem, such as invalid credentials or an unreachable address. Connectivity issues are also surfaced directly in the upstream status column.

Each row in the upstreams table now shows the number of indexed packages, and can be expanded to reveal further detail — including the last indexed timestamp, GPG key details, and distributions.

A reindex action is now available for each upstream.

Upstreams can now be updated without re-entering a password when authentication is enabled.

The upstreams table is now sorted in priority order.

For even greater insight into upstream activity, see 

Track and troubleshoot upstream requests with logs

Set up and monitor upstreams more effectively

Upstream logs are now available in the web app. Each upstream's log shows successful requests from the last 12 hours and failed requests from the last 24 hours, making it easier to monitor activity and diagnose issues as they arise.

This is part of a wider set of improvements to upstreams — see 

 to sunset our old documentation website. The old website has now been retired, and redirects are in place to our 

Today we're releasing an improved search experience on the new docs site. Search is now more prominent in the user experience. Results are much more accurate, and organized into helpful categories - showing results from core documentation, handy guides, and our API reference. As ever, if you have any feedback please 

Improved search experience in Cloudsmith documentation

Teams with UK data residency requirements can now store artifacts on UK infrastructure. Select 

 as your storage region when creating a new repository, or transfer an existing one via a repository's Settings.

Learn more about custom storage regions in 

London is now a supported storage region

You can now connect multiple repositories to a single repository, giving your teams a single repo to pull every package they need. This allows you to organize your artifacts by Line of Business (LOB) while ensuring that shared internal libraries and vendor images are managed centrally and remain always available to the teams that need them.

Enterprises need to balance easy access to artifacts with strict control over who can publish or promote them. Previously, the only way to aggregate repositories in Cloudsmith was through "Cloudsmith-to-Cloudsmith" upstreams. Because this wasn't a native fit for complex workflows, it introduced indexing delays and performance overhead that didn't meet the needs of large-scale delivery pipelines.

Connected repositories provide a native solution that offers:

Developers no longer need prior knowledge of the underlying repo structure. By connecting repositories, you present a single, shared location for builders to fetch any required image or package.

Unlike older methods, there is no indexing delay. When a team pushes a new library or image to a connected repository, it is immediately available to every team that needs it.

You can manage vendor and shared libraries "behind the scenes," isolating your developers from the underlying complexity of how you manage permissions and access control.

Connected repositories are built for workspace administrators who need a performant, unified way to distribute packages across a complex organization without re-architecting their existing delivery workflows.

Packages are visible to consumers of the source repository the moment they are pushed, eliminating the need for secondary indexing.

Set clear rules for which repository "wins" if the same package version exists in multiple places, ensuring deterministic and secure builds.

 If your shared library repository points to external sources like Maven Central or PyPI, your LOB repositories get access to those public packages automatically.

Administrators can manage these connections via the UI or API, ensuring a consistent and auditable structure across the entire organization.

 and contact us to enable Connected Repositories for your workspace.

Recover deleted packages within a 7-day restoration window

What's new

Getting started

Other logs

Make Cloudsmith yours with personalized tables

Set up and monitor upstreams more effectively

Track and troubleshoot upstream requests with logs

Improved search experience in Cloudsmith documentation

London is now a supported storage region

Architect a scalable, developer-friendly repository structure with connected repositories