With the new cloudsmith_connected_repository resource for the Cloudsmith Terraform provider, you can define connected repository configurations in code alongside the rest of your Cloudsmith infrastructure.
You can now declare connected repository configurations alongside your other Cloudsmith resources, apply them through standard terraform apply workflows, and track changes in version control.
provider "cloudsmith" {
api_key = "my-api-key"
}
data "cloudsmith_organization" "my_organization" {
slug = "my-organization"
}
resource "cloudsmith_repository" "source" {
description = "Source repository"
name = "source-repo"
namespace = data.cloudsmith_organization.my_organization.slug_perm
}
resource "cloudsmith_repository" "target" {
description = "Target repository"
name = "target-repo"
namespace = data.cloudsmith_organization.my_organization.slug_perm
}
resource "cloudsmith_repository_connected" "link" {
namespace = cloudsmith_repository.source.namespace
repository = cloudsmith_repository.source.slug_perm
target_repository = cloudsmith_repository.target.slug
is_active = true
priority = 1
}
For more information about managing connected repositories with the Cloudsmith Terraform provider, see Terraform Registry: Cloudsmith - Repository Connected Resource.
Connected repositories are in early access and are currently supported for Maven, Docker, Python, NPM, Go, Cargo (Rust), NuGet, Helm, Conda, and Conan. Please contact us if you are interested in trying them.
For more information about connected repositories, see our documentation.
By default, Cloudsmith assigns the `latest` dist-tag to the package with the highest semantic version number, which may not match what the upstream registry considers `latest`. A new per-repository setting, npm upstream tags take precedence, lets upstream distribution tags (dist-tags) override Cloudsmith’s semantic versioning (SemVer)-based tag assignment…
A cooldown policy now filters non-compliant package versions from the repository index before package managers ever see them. This provides both security control and a better developer experience: clean resolution to the next compliant version, no build failures, and no waiting…
Cloudsmith CLI Action v1 is now deprecated. Security-only patches will continue until 31st December 2026, after which v1 reaches end-of-life (EOL). Migrate to v2 before 31st December 2026 to avoid disruption…
We're rolling out improvements to how Cloudsmith evaluates relational version ranges across the platform to ensure clearer and more predictable results for semantic version searches and version-based ordering…
Private Broadcasts lets you put your brand front and center throughout the entire distribution experience, distributing software securely to your partners, customers and internal users through your own branded portal. Full customization and built-in analytics give you control over the experience and visibility into adoption, while entitlement tokens keep access tightly managed, so your software reaches exactly the right people…
Multi-select package actions now support delete. Select up to 100 packages and remove them in a single action. Deleted packages will be moved to recently deleted packages for 7 days…