126 wires and counting

$ follow HashiCorp

Keep up with HashiCorp in about 3 minutes: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

or

fair warning: these emails are deeply technical. diffs, version numbers, CVEs, benchmark deltas. if that's not your idea of a good read, this isn't your newsletter.

Folds into your digest — weekly by default, monthly if you prefer. Unsubscribe in one click.

$ status

wire 2026-07-03
stories 17

© 2026 RepoJournal Home Showcase Explore How it works Privacy

$ the-wire · showcase

CONSUL ADDS ENTERPRISE EXTERNAL AUTH LAYER, DOCS SHED DEPRECATED HVAULT CODE

By RepoJournal · Filed · About HashiCorp · Composed from the cited sources · methodology

Consul's API Gateway now supports external authorization enforcement through a new enterprise-only surface, while the docs team systematically removes HashiVault references across the unified platform.

Consul shipped a three-layer config model for external authorization (`ext_authz`) on its API Gateway [1], with the enforcement behavior gated to enterprise customers while the shared CE surface ships in the open codebase. This keeps the feature invisible in community editions but ready for enterprise deployments without additional maintenance burden. The release is backed by fresh hygiene workflows [2] that will catch release engineering issues before they ship, though these checks run non-blocking initially to let teams adjust. On the docs front, HashiVault references are being systematically purged from the Vault Secrets Operator, API references, and supporting materials [3][4], with proper redirect chains already verified and HVS CLI docs moved to the deprecated directory [4]. A separate fix addresses a malformed table in the explorer API reference . Packer's plugin SDK caught up on module dependencies and fixed an unchecked error condition [5], a small but necessary hygiene win.

Quick answers

What shipped in HashiCorp on July 3, 2026?
Consul's API Gateway now supports external authorization enforcement through a new enterprise-only surface, while the docs team systematically removes HashiVault references across the unified platform. In total, 11 commits and 6 pull requests landed.
Who contributed to HashiCorp on July 3, 2026?
4 developers shipped this update, including bharath-k1999, riya-bhatia-26, jonathanfrappier, and tanmay-hc.
What were the notable HashiCorp updates?
config-entry(api-gateway): add ext_authz filter surface (Enterprise only), Adding release hygiene workflows, and Claude VSO cleanup.