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-10-13
stories 2

© 2026 RepoJournal Home Showcase How it works Privacy

$ the-wire · showcase

consul-k8s corrects the allowed PII value set

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

A one-line correction to consul-k8s's PII validation landed as the day's only shipped change, fixing an allowed-values mismatch in the IPC path.

fix the allowed values for PII hashicorp/consul-k8s

by vdinesh4738

The fix resets the accepted PII values in IPC to placeholder, mask, block, and off, so configuration that previously failed validation against a mismatched list should now be accepted as written. Anyone relying on the old set should re-check their values against these four.

fix the allowed values for PII (#5723) hashicorp/consul-k8s

by vdinesh4738

The correction is on main, with the changelog entry added alongside it, which puts it in line for the next consul-k8s release rather than in a published version today.

Quick answers

What shipped in HashiCorp on October 13, 2026?
A one-line correction to consul-k8s's PII validation landed as the day's only shipped change, fixing an allowed-values mismatch in the IPC path. In total, 1 commits and 1 pull requests landed.
Who contributed to HashiCorp on October 13, 2026?
1 developer shipped this update, including vdinesh4738.
What were the notable HashiCorp updates?
fix the allowed values for PII and fix the allowed values for PII (#5723).