RepoJournal
HashiCorp

@hashicorp

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

Pick a date

  1. Wed 27 may
  2. Thu 28 may
  3. Fri 29 may
  4. Sat 30 may
  5. Sun 31 may
  6. Mon 1 jun
  7. Mon 8 jun
  8. Tue 9 jun
  9. Wed 10 jun
  10. Thu 11 jun
  11. Fri 12 jun
  12. Sat 13 jun
  13. Sun 14 jun
  14. Mon 15 jun
  15. Tue 16 jun
  16. Wed 17 jun
  17. Thu 18 jun
  18. Fri 19 jun
  19. Sat 27 jun
  20. Sun 28 jun
  21. Tue 30 jun
  22. Wed 1 jul
  23. Thu 2 jul
  24. Fri 3 jul
  25. Sat 4 jul
  26. Sun 5 jul
  27. Mon 6 jul
  28. Tue 7 jul
  29. Wed 8 jul
  30. Today 9 jul

The Wire · Showcase

PACKER SHIPS TIMESTAMP FUNCTIONS, CONSUL-K8S TIGHTENS DEPS

By RepoJournal · Filed · About HashiCorp

Packer finally closes the timestamp gap with two new HCL functions that match Terraform's behavior, while Consul-K8s hardens its dependency stack across three critical libraries.

Packer added `rfc3339_parse()` and `unix_timestamp_parse()` functions [1] to close a long-standing gap in HCL2 templates. Since the JSON engine retired, users had no way to generate Unix timestamps without external variable injection. These functions intentionally match the Terraform time provider [1] so both tools behave identically. Packer also shipped support for `optional()` attributes in variable object types [4], aligning its HCL parser with Terraform's stricter type constraints. On the Consul side, Consul-K8s bumped three key dependencies: consul/api to v1.34.4, serf to v0.10.4, and go-metrics to v0.6.0 [2], plus upgraded Alpine to 3.24 [3] across its container images. Boundary provider extended session recording and storage bucket support to RDP targets [5], a feature previously limited to SSH, while also updating its SDK to v0.0.60 and API to v0.0.62 [6]. Consul-ESM prepped version 0.11.0 [7] and suppressed a Go security advisory where no fix is available [8].

Action items

References

  1. [1] FEAT: Add rfc3339_parse and unix_timestamp_parse HCL functions ↗ hashicorp/packer
  2. [2] update dependencies: bump hashicorp/consul/api to v1.34.4, hashicorp/serf to v0.10.4, and hashicorp/go-metrics to v0.6.0 ↗ hashicorp/consul-k8s
  3. [3] update alpine to 3.24 ↗ hashicorp/consul-k8s
  4. [4] core/hcl2: support optional() attributes in variable object types ↗ hashicorp/packer
  5. [5] feat(target): Support session recording and storage buckets for RDP targets ↗ hashicorp/terraform-provider-boundary
  6. [6] chore: Update Boundary SDK & API Versions ↗ hashicorp/terraform-provider-boundary
  7. [7] Merge pull request #388 from hashicorp/prep_0.11.0 hashicorp/consul-esm
  8. [8] suppressing "GO-2026-5932" as fix not available hashicorp/consul-esm

FAQ

What changed in HashiCorp on July 9, 2026?
Packer finally closes the timestamp gap with two new HCL functions that match Terraform's behavior, while Consul-K8s hardens its dependency stack across three critical libraries.
What should HashiCorp teams do about it?
Review and merge Packer timestamp functions for templates using date calculations • Update Consul-K8s dependencies and Alpine base image in your builds • Test Boundary RDP session recording if you use that feature
Which HashiCorp repositories shipped on July 9, 2026?
hashicorp/packer, hashicorp/consul-k8s, hashicorp/terraform-provider-boundary, hashicorp/consul-esm

Related across the cluster

For your repos

The showcase is a teaser.
Your wire is the product.

Same engine. Different stack. Below: what changes when the wire is yours.

Showcase wire

  • •14 famous open source orgs
  • •One wire per day
  • •Public, generic
  • •Read on the web, when you remember

Your wire

  • →Up to 1,500 of your repos - orgs, deps, vendors
  • →Morning and evening briefs
  • →Action items routed to your team
  • →Slack delivery, email, breaking-news CVE alerts

Want a hands-on demo first? Ask a current user for an invite link.