Private packages, every ecosystem
Connect the registries that serve your private packages, whether they hold npm packages, Terraform modules, Python, NuGet, Go or Cargo, and every run installs them the way your own engineers do.
Few codebases install only public packages. Internal libraries, shared Terraform modules and a design system sit in private registries, and a run that cannot reach them either fails or works around code it should have used.
Taiga now connects to the registries behind every ecosystem it builds in: npm, Terraform, Python, NuGet, Go and Cargo, from GitHub Packages and Artifactory to HCP Terraform, Azure Artifacts and Google Artifact Registry. A connection is tested before it is saved, against a package your repositories install when you name one, so a credential that cannot read your packages is refused on the spot. The credential is stored encrypted, handed to agents only while a run needs it, and never written into your repository.
A registry nobody has connected yet is a task, not a broken build. The run keeps going, an action-required item names the registry to connect, and the pull request says the change was not verified locally, leaving your own CI as the check.