RepoJournal
HashiCorp

@hashicorp

Terraform, Vault, Consul — infra-as-code for ops teams

Pick a date

  1. Sun 3 may
  2. Tue 5 may
  3. Wed 6 may
  4. Thu 7 may
  5. Fri 8 may
  6. Sat 9 may
  7. Sun 10 may
  8. Mon 11 may
  9. Tue 12 may
  10. Wed 13 may
  11. Thu 14 may
  12. Fri 15 may
  13. Sat 16 may
  14. Sun 17 may
  15. Tue 19 may
  16. Wed 20 may
  17. Thu 21 may
  18. Sat 23 may
  19. Sun 24 may
  20. Mon 25 may
  21. Tue 26 may
  22. Wed 27 may
  23. Thu 28 may
  24. Fri 29 may
  25. Sat 30 may
  26. Sun 31 may
  27. Mon 1 jun
  28. Mon 8 jun
  29. Tue 9 jun
  30. Today 10 jun

The Wire · Showcase

REGISTRY TAGGING GOES BETA ACROSS TERRAFORM ENTERPRISE

By RepoJournal · Filed · About HashiCorp

HashiCorp's Terraform Enterprise SDK now supports tagging modules, providers, and component configs — a capability that's been in development and just landed in go-tfe.

The go-tfe client library shipped registry-tagging support [1] for modules, providers, and component configs in beta phase, adding critical APIs for tagging resources already deployed in your registry. This lands alongside permission expansion [2] that introduces CanReadStateVersions and CanReadVariable checks, giving operators finer-grained control over who can access what in your Terraform Enterprise environments. On the dependency front, Vault Secrets Operator pulled in 12 updates [3] across the go ecosystem — notably terratest 0.55→0.56 and go-version 1.8→1.9 — all backward-compatible and ready to ship. The JavaScript desk upgraded axios to 1.16.0 [4], which adds QUERY method support and closes a substantial backlog of HTTP adapter bugs around redirects and timeouts. All changes maintain compatibility with existing integrations.

Action items

References

  1. [1] Add registry-tagging support for modules, providers and component configs ↗ hashicorp/go-tfe
  2. [2] Add CanReadStateVersions and CanReadVariable ↗ hashicorp/go-tfe
  3. [3] Bump the gomod-backward-compatible group across 1 directory with 12 updates ↗ hashicorp/vault-secrets-operator
  4. [4] build(deps): bump axios from 1.15.1 to 1.16.0 ↗ hashicorp/js-releases

FAQ

What changed in HashiCorp on May 5, 2026?
HashiCorp's Terraform Enterprise SDK now supports tagging modules, providers, and component configs — a capability that's been in development and just landed in go-tfe.
What should HashiCorp teams do about it?
Review registry-tagging beta docs and test against non-prod Terraform Enterprise environments • Upgrade Vault Secrets Operator dependencies in CI before next release candidate • Bump axios to 1.16.0 if you depend on HTTP redirect handling in Node services
Which HashiCorp repositories shipped on May 5, 2026?
hashicorp/go-tfe, hashicorp/vault-secrets-operator, hashicorp/js-releases

Related across the cluster

For your repos

The showcase is a teaser.
Your wire is the product.

Same engine. Different stack. Below: what changes when the wire is yours.

Showcase wire

  • •14 famous open source orgs
  • •One wire per day
  • •Public, generic
  • •Read on the web, when you remember

Your wire

  • →Up to 1,500 of your repos - orgs, deps, vendors
  • →Morning and evening briefs
  • →Action items routed to your team
  • →Slack delivery, email, breaking-news CVE alerts

Want a hands-on demo first? Ask a current user for an invite link.