OpenTofu Registry Weekly: New Providers, Modules, and Version Bumps

I looked at the last seven days of commits in the opentofu/registry repository, the open registry that serves provider and module metadata for OpenTofu. The repo saw about 300 commits in the window. Most of them are automated version bumps, but a steady stream of new providers and modules landed too, including the Anthropic provider and a Technitium provider. If you pin provider versions, this week probably already touched your lock files.

Two new providers worth a look

The merge queue added the Anthropic provider on October 17 via the Anthropic provider pull request (#5874). If you manage AI related infrastructure with OpenTofu, it is now installable with a normal required_providers block.

The same day brought the Technitium DNS provider through PR #5876. Technitium is a common self hosted DNS server, so having a provider published in the registry removes the need for a local filesystem mirror.

terraform {
  required_providers {
    anthropic = {
      source  = "registry.opentofu.org/anthropic/anthropic"
      version = "~> 0.1"
    }
  }
}

Earlier in the week, merges added a ClickHouse provider key (PR #5870), MongoDB provider metadata (PR #5847), the Aikido provider with two entries (PR #5849 and PR #5851), and providers from vlazic for Convex and Opalstack (PR #5854, PR #5843).

New modules for AWS and Spacelift setups

Module activity clustered around AWS. The Spacelift self hosted stack got two entries: the terraform-aws-spacelift-selfhosted module (#5865) and its IAM companion module (#5866). If you run Spacelift workers in your own AWS account, both pieces are now reachable from the OpenTofu registry.

A SES plus Cloudflare module from stephops also merged on October 17 in PR #5872, wiring Amazon SES receiving with Cloudflare DNS records. On the vendor side, BrightDotAi added an S3 tables provider and key on October 14 and 15 (PR #5858, PR #5860).

What the automated commits are doing

The bulk of the 300 commits come from the OpenTofu Core Development Team running automated version bumps. Commits like an automated bump for providers starting with i and another batch for modules appear many times per day, split alphabetically.

Each bump writes discovery metadata into the per provider JSON files. The diff excerpt for the latest commit shows a typical case in providers/i/irashack/pocketid.json: version 3.1.4 first failed discovery with “checksums not found in release”, then the next pass recorded the full target list with sha256 and h1 hashes, and dropped the error entry. The registry retries releases that are incomplete at discovery time, which is the behavior you want since maintainers often publish assets after tagging.

Busiest files this week are good examples of active providers. The Defense Unicorns UDS provider file changed in 21 commits, and c2devel croccloud in 17. Rapid release cadence upstream shows up as frequent registry updates.

How to prepare

Three things to keep in mind:

• If a provider version shows up in your index but fails install with a checksum error, wait an hour and retry. The registry self heals once the upstream release is complete, as the pocketid diff shows.
• New provider keys can take a couple of entries to settle: a namespace or key rename landed as separate PRs twice this week (Aikido, BrightDotAi, vlazic). Check terraform providers mirror output after upgrading lock files.
• The bump commits are fully automated. If you track the repo, they are noise; follow the PR merges instead for real changes.

Worth following if you consume provider modules from OpenTofu, since new provider availability is the main user visible change here, and this week delivered plenty of it.