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).

@hashicorp

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

github ↗

Pick a date

Topics: Go Infrastructure Full archive →

The Wire · Showcase

TERRAFORM PROVIDER CLEANUP PUSHES FORWARD; CONSUL HARDENS RELEASE PIPELINE

By RepoJournal · Filed 06:57 UTC on August 6, 2026 · About HashiCorp

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

→ Review and merge Azure provider feature flag removals before next release hashicorp/terraform-provider-azurerm [plan]
→ Upgrade to Go 1.26.5 in dataplane and k8s if not already merged hashicorp/consul-dataplane [plan]
→ Validate Terraform Vault PKI changes in test environment to confirm no spurious diffs hashicorp/terraform-provider-vault [monitor]
→ Test CA certificate trust in Consul Helm deployments with latest chart hashicorp/consul-k8s [plan]

References

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

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).

TERRAFORM AWS PROVIDER SHIPS MAJOR VERSIONS WITH ELASTICACHE AND ECS EXPANSIONS

Terraform AWS provider v6.34.0 through v6.57.1 landed overnight with ElastiCache fixes, new ECS capacity reservation support, and the second MailManager resource joining the roster.

go 68 shipped

@hashicorp Aug 4

TERRAFORM GRAPH INTERNALS STRIPPED FOR SPEED

James Bardin just yanked five layers of unused abstractions out of Terraform's core graph engine, clearing the path for what comes next.

go 25 shipped

@hashicorp Aug 3

AWS SDK gets patched across the stack

Go-getter pulled in the latest AWS SDK updates, while memberlist tightened its metrics dependencies and the design system cut asset bloat by nearly 60 percent.

go 7 shipped

@hashicorp Aug 2

CONSUL BUMPS GO TO 1.26.5, NIGHTLY BUILDS LIVE

Consul shipped a Go version update overnight while Nomad tooling pushed fresh development snapshots to testers.

go 4 shipped

Elsewhere on the wire

AI Agents Aug 6

LANGCHAIN HARDENS ANTHROPIC TOOL CALLING AND GIT CREDENTIALS AS OPENHANDS SHIPS 1.10.0

LangChain fixed a critical credential leak in evaluation runs while Anthropic tool schemas get proper fallback handling, as three major agent frameworks push releases across the ecosystem.

ai-agents 54 shipped

Local LLMs Aug 6

OLLAMA FIXES KV CACHE CORRUPTION, LLAMA.CPP HARDENS FILE SEARCH, VLLM KILLS MOE LEGACY CODE

Ollama patched a critical cache corruption bug that corrupts lazy snapshots during multi-request prefills, while llama.cpp hardened Windows junction traversal and vLLM removed 14 hardcoded MoE shards across quantization methods.