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-09-17
stories 50

© 2026 RepoJournal Home Showcase Explore How it works Privacy

$ the-wire · showcase

Consul turns on post-quantum key exchange by default

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

Consul now injects X25519MLKEM768 as a default ECDH curve whenever a mesh direction sets TLSv1_3, changing cipher negotiation for every Connect sidecar on the upgraded control plane.

feat(connect): enabling Post-Quantum Cryptography (PQC) hybrid key exchange across Consul Connect Envoy service mesh sidecars. hashicorp/consul

by nitin-sachdev-29

Consul now injects ["X25519MLKEM768", "X25519"] automatically whenever tls_min_version is TLSv1_3, defaults TlsMaximumProtocolVersion to TLSv1_3, and adds ECDHCurves to MeshDirectionalTLSConfig alongside new agent/config fields for operators. The PR describes the work as Part 1 of enabling hybrid key exchange (X25519MLKEM768, NIST FIPS 203) across Connect Envoy sidecars and agent TLS communicat...

Add release hygiene workflow hashicorp/consul

by riya-bhatia-26

The new workflow scans both the PR description and every changed source or config file for internal Jira ticket IDs, with BUSL and MPL added to EXCLUDE_KEYS so SPDX license headers don't trip it. Contributor workflow change only: expect PRs to fail the check until ticket references are stripped.

Adding client side check for jira IDs hashicorp/consul

by riya-bhatia-26

A client-side pre-commit check now blocks Jira IDs (IPENG-123, CONSUL-456) across three surfaces: staged file content, the branch name at checkout, and the commit message before it is recorded. It catches leaks at the developer's workstation rather than at PR review.

Adds caching to `fwtypes.AttributeTypes` hashicorp/terraform-provider-aws

by gdavison

Caching added to fwtypes.AttributeTypes in terraform-provider-aws. Framework provider paths that reconstruct attribute types repeatedly should do less of that work.

[chore] swissshepherd fixes: RDS hashicorp/terraform-provider-aws

by YakDriver

RDS chore among the provider's Swiss Shepherd cleanup work; the remaining provider traffic is list-resource groundwork, including aws_wafv2_ip_set, aws_network_acl with its RI counterpart, and aws_rds_cluster_instance, plus a Go 1.26.6 bump in copywrite.

Quick answers

What shipped in HashiCorp on September 17, 2026?
Consul now injects X25519MLKEM768 as a default ECDH curve whenever a mesh direction sets TLSv1_3, changing cipher negotiation for every Connect sidecar on the upgraded control plane. In total, 34 commits, 15 pull requests, and 1 releases landed.
Who contributed to HashiCorp on September 17, 2026?
7 developers shipped this update, including Ritik Rajdev, YakDriver, subham-ibmhc, gdavison, johnsonaj, nitin-sachdev-29, and riya-bhatia-26.
What were the notable HashiCorp updates?
feat(connect): enabling Post-Quantum Cryptography (PQC) hybrid key exchange across Consul Connect Envoy service mesh sidecars, Add release hygiene workflow, and Adding client side check for jira IDs.