Cloudsmith Changelog

We have now fully deprecated our old documentation website, and improved the search experience on our new docs website…

Teams with UK data residency requirements can now store artifacts on UK infrastructure. Select London as your storage region when creating a new repository, or transfer an existing one via a repository's Settings…

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…

We’ve released v2.0.0 of the Cloudsmith CircleCI Orb, bringing it to full feature parity with our GitHub Actions and Azure DevOps integrations. This update focuses on security through OIDC, improved reliability, and greater flexibility for your CI/CD workflows…

We’ve added support for the Wolfi ecosystem, alongside the ability to proxy and cache both Alpine and Wolfi packages from their public mirrors. For teams installing packages via APK, this provides a simpler, more reliable way to manage dependencies by using Cloudsmith as a single source for both public and private packages…

We’ve released a major update to the Cloudsmith VS Code extension, transforming it from a repository browser into a proactive part of your software supply chain security. By integrating security remediation, automated Infrastructure as Code (IaC) generation, and dependency health tracking directly into the IDE, we’ve eliminated the friction between writing code and managing a secure software supply chain…

Cloudsmith has introduced a new vulnerabilities command to the CLI, allowing users to retrieve package security scan results through a single command…

Upstream Trust prevents attackers from hijacking your internal package names in public repositories. By defining explicit trust boundaries, you ensure that once an artifact is identified as internal, it cannot be replaced by an untrusted externally-sourced version…

Policy as code is a powerful way to scale security and compliance across modern DevOps pipelines, but writing Rego from scratch is a high barrier to entry. We’ve introduced Policy Templates to provide functional starting points, allowing you to deploy validated security guardrails without coding from scratch…

Following our recent update to include cache data in Client Log Exports, we have now added the ability to filter by Edge Response directly within the Client Logs UI…