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-07
stories 45
GitHub RSS Archive Reviews

© 2026 RepoJournal Home Showcase How it works Privacy

$ the-wire · showcase

CONSUL API GATEWAY FIX STOPS 503 CASCADES IN MULTI-PARTITION SETUPS

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

kt shani34 santoshpulluri dependabot gbaker-ibm shashankNandigama
6 people shipped this
kt @katbyte 5 cited shani34 @shani34 2 cited santoshpulluri @santoshpulluri 2 cited dependabot @dependabot 1 cited gbaker-ibm @gbaker-ibm shashankNandigama @shashankNandigama

Consul Enterprise users hitting HTTP 503s after upgrading to 2.0.x now have a fix: API gateways with HTTP listeners were resolving downstream services with wrong protocols, breaking discovery chains in peered clusters.

The root cause is in gateway synthesis. When API gateways compose service-router destinations, they were resolving backends as TCP by default instead of respecting HTTP protocol overrides, triggering cluster_not_found errors in multi-partition and cluster-peering topologies [1] [2]. This fix resolves composed service-router destinations as HTTP during gateway synthesis, eliminating the protocol mismatch that cascaded into widespread 503s. Meanwhile, Consul dataplane is quieting noisy logs from UDP timeout chatter [4] [5], and gRPC bumped to 1.82.1 with security hardening against frame flood attacks [3]. On the Azure provider side, the team is cleaning house by removing all 5.0 feature flag gates across legacy, monitor, containers, arc-kubernetes, authorization, automation, batch, and ioThub modules [6] [7] [8] [9] [10], signaling that 5.0 is now the stable baseline and legacy code paths can be junked.

Action items

References

  1. [1] fix(apigw): resolve composed service-router destinations as http during gateway synthesis ↗ hashicorp/consul
  2. [2] fix(apigw): resolve composed service-router destinations as http during gateway synthesis (#23793) ↗ hashicorp/consul
  3. [3] Bump google.golang.org/grpc from 1.72.2 to 1.82.1 in /integration-tests ↗ hashicorp/consul-dataplane
  4. [4] Removal of noisy log ↗ hashicorp/consul-dataplane
  5. [5] Removal of noisy log (#1198) ↗ hashicorp/consul-dataplane
  6. [6] remove 5.0 feature flag gates from legacy (#32993) ↗ hashicorp/terraform-provider-azurerm
  7. [7] remove 5.0 feature flag gates from monitor (#32990) ↗ hashicorp/terraform-provider-azurerm
  8. [8] remove 5.0 feature flag gates from arckubernetes, authorization, automation and batch (#32994) ↗ hashicorp/terraform-provider-azurerm
  9. [9] remove 5.0 feature flag gates from containers (#32991) ↗ hashicorp/terraform-provider-azurerm
  10. [10] remove 5.0 feature flag gates from iothub (#32995) ↗ hashicorp/terraform-provider-azurerm

$ 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 7, 2026?
Consul Enterprise users hitting HTTP 503s after upgrading to 2.0.x now have a fix: API gateways with HTTP listeners were resolving downstream services with wrong protocols, breaking discovery chains in peered clusters. In total, 21 commits and 24 pull requests landed.
Who contributed to HashiCorp on August 7, 2026?
6 developers shipped this update, including gbaker-ibm, shani34, dependabot, shashankNandigama, santoshpulluri, and kt.
What were the notable HashiCorp updates?
fix(apigw): resolve composed service-router destinations as http during gateway synthesis, fix(apigw): resolve composed service-router destinations as http during gateway synthesis (#23793), and Bump google.golang.org/grpc from 1.72.2 to 1.82.1 in /integration-tests.
♥

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