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-06-27
stories 10

© 2026 RepoJournal Home Showcase How it works Privacy

$ the-wire · showcase

BOUNDARY WORKER HELM OVERHAULS TEST MATRIX, NOMAD AUTOSCALER SHIPS JSONENCODE SUPPORT

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

Boundary's Kubernetes validation just got real - switching from KIND binaries to actual versioned nodes means the chart now proves it works on the K8s versions you're actually running.

The big structural win comes from boundary-worker-helm [1], which ditched a validation theater approach that downloaded KIND binaries without actually testing against different Kubernetes API server versions. Now each CI run targets a specific kindest/node image pinned to real K8s releases and runs them in parallel, so you know the chart ships tested on 1.26, 1.27, and beyond. On the policy authoring side, nomad-autoscaler landed jsonencode support [2] for file-based policies, which means users writing APM queries can stop hand-escaping JSON strings and write readable HCL objects instead. The Instana plugin integration just got less painful. All three Nomad ecosystem projects pushed nightly snapshots [3][4][5], so if you're running bleeding edge, pull and test before the next stable cut. Compliance automation also caught up with boundary-worker-helm PR template updates [6][7] - standard HCP boundary compliance stuff, review and merge to stay in good standing.

Action items

References

  1. [1] Convert acceptance matrix from KIND-binary to Kubernetes-version, parallelize in CI ↗ hashicorp/boundary-worker-helm
  2. [2] enable jsonencode in file policy decoding ↗ hashicorp/nomad-autoscaler
  3. [3] nightly ↗ hashicorp/nomad-autoscaler
  4. [4] nightly ↗ hashicorp/nomad-driver-podman
  5. [5] nightly ↗ hashicorp/nomad-pack
  6. [6] [Compliance] - PR Template Changes Required ↗ hashicorp/boundary-worker-helm
  7. [7] [Compliance] - PR Template Changes Required (#55) ↗ hashicorp/boundary-worker-helm

Quick answers

What shipped in HashiCorp on June 27, 2026?
Boundary's Kubernetes validation just got real - switching from KIND binaries to actual versioned nodes means the chart now proves it works on the K8s versions you're actually running. In total, 4 commits, 3 pull requests, and 3 releases landed.
Who contributed to HashiCorp on June 27, 2026?
3 developers shipped this update, including AbhiMgowda, hashi-divyansh, and compliance-pr-automation-bot[bot].
What were the notable HashiCorp updates?
Convert acceptance matrix from KIND-binary to Kubernetes-version, parallelize in CI, enable jsonencode in file policy decoding, and nightly.