RepoJournal
HashiCorp @hashicorp
176 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-08-06
stories 36
GitHub RSS Archive Reviews

© 2026 RepoJournal Home Showcase How it works Privacy

$ the-wire · showcase

TERRAFORM PROVIDER CLEANUP PUSHES FORWARD; CONSUL HARDENS RELEASE PIPELINE

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

kt P Ajay Rao shashankNandigama hellobontempo shani34 Manishakumari-hc
6 people shipped this
kt @katbyte 5 cited P Ajay Rao @pajay-rao 2 cited shashankNandigama @shashankNandigama 2 cited hellobontempo @hellobontempo 2 cited shani34 @shani34 1 cited Manishakumari-hc @Manishakumari-hc

HashiCorp is systematically removing feature flags across the Azure provider while Consul teams move security scanning upstream in their release workflows.

The terraform-provider-azurerm team is executing a coordinated cleanup of 5.0 feature flag gates across multiple service modules [1][2][3][4][5], signaling a major version consolidation that removes technical debt ahead of production deployments. On the Consul side, both dataplane and k8s repositories are embedding CVE scanning directly into release pipelines rather than waiting for downstream verification [7][9], with dataplane now automating release branch preparation and binary scanning in a new .release/release-scripts directory. Consul-dataplane also moved to Go 1.26.5 to patch multiple security vulnerabilities [6][8], while terraform-provider-vault fixed an unintended resource replacement issue in its PKI certificate generation by removing default values that were triggering false diffs [11][12]. The Helm-based CA trust fix in consul-k8s addresses a production gotcha where custom CAs supplied via global.trustedCAs were present but never actually trusted because OpenSSL requires subject-hash symlinks to discover certificates in a directory [10].

Action items

References

  1. [1] remove 5.0 feature flag gates from eventgrid (#32971) ↗ hashicorp/terraform-provider-azurerm
  2. [2] remove 5.0 feature flag gates from datafactory (#32899) ↗ hashicorp/terraform-provider-azurerm
  3. [3] remove 5.0 feature flag gates from analysisservices and applicationinsights (#32896) ↗ hashicorp/terraform-provider-azurerm
  4. [4] remove 5.0 feature flag gates from apimanagement (#32895) ↗ hashicorp/terraform-provider-azurerm
  5. [5] remove 5.0 feature flag gates from bot, cdn, cognitive, communication and containerapps (#32900) ↗ hashicorp/terraform-provider-azurerm
  6. [6] Addition of security permissions to security-scan.yml (#1211) ↗ hashicorp/consul-dataplane
  7. [7] release enhancements ↗ hashicorp/consul-dataplane
  8. [8] Updating mulitple go packages to fix SECVULN issue ↗ hashicorp/consul-dataplane
  9. [9] Add a GHA workflow to scan binaries and images (#5512) ↗ hashicorp/consul-k8s
  10. [10] fix(helm): global.trustedCAs certificates are never trusted (missing OpenSSL hash symlinks) ↗ hashicorp/consul-k8s
  11. [11] Add pkcs12_bundle and jks_bundle format support for PKI cert generation (without defaults) ↗ hashicorp/terraform-provider-vault
  12. [12] Add pkcs12_bundle and jks_bundle format support for PKI cert generation (without defaults) (#2950) ↗ hashicorp/terraform-provider-vault

$ ls hashicorp/reviews/ # the step-back reads

the week in review Consul provider patches two Go CVEs, adds 2.23.0 upgrade gate the month in review Consul patches four CVEs as Go bumps sweep repos
Full archive → Weekly reviews →

Quick answers

What shipped in HashiCorp on August 6, 2026?
HashiCorp is systematically removing feature flags across the Azure provider while Consul teams move security scanning upstream in their release workflows. In total, 18 commits and 18 pull requests landed.
Who contributed to HashiCorp on August 6, 2026?
6 developers shipped this update, including kt, P Ajay Rao, shashankNandigama, Manishakumari-hc, shani34, and hellobontempo.
What were the notable HashiCorp updates?
remove 5.0 feature flag gates from eventgrid (#32971), remove 5.0 feature flag gates from datafactory (#32899), and remove 5.0 feature flag gates from analysisservices and applicationinsights (#32896).
♥

$ log @hashicorp --recent

A copyright sweep is the whole day 2 shipped HashiCorp: no material update 2 shipped Application Design Center lands, workload identity pools grow two fields 46 shipped Consul CI breaks on jq 1.8 as Ubuntu 26.04 runners arrive 31 shipped

$ log --all # elsewhere on the wire

Agent Security Quiet day in agent security as guard coverage reaches four clients Alignment & Post-training verl defaults Ascend RL mode, open-instruct unblocks SFT packing

$ ls showcases/

Safety Evals AI Red Teaming Agent Security Interpretability Alignment & Post-training

$ init your-desk

RepoJournal can write one of these for any repo you care about. Sign in with GitHub, pick your repos and sources, and your desk gets a wire like this one every morning.