Long-line logging no longer fails with token too long
This release1 fixBug fixesAI-tallied from the release notesFixed bufio.Scanner: token too long errors when logging requests or responses containing long lines.
npx @buildinternet/releases get hashicorpVault 2.2.0 landed with container and PostgreSQL storage changes that break existing setups, and Vault 2.1 reached HCP Vault Dedicated.
Vault 2.2 breaks container and PostgreSQL storage setups.
cap_ipc_lock; set disable_mlock = true and disable swap on the hostTerraform Policy is generally available.
-policies on plan, apply, and query no longer requires an experimental build or -allow-experimental-features-minimal-refresh refreshes only resources with proposed changesConsul's transparent proxy setup moved to nftables (breaking). consul connect redirect-traffic applies IPv4 and IPv6 rules atomically through the nftables inet family, and validates exclusions up front — numeric user IDs, IP or CIDR outbound exclusions. It does not remove iptables/ip6tables rules left by earlier versions, so strip those before upgrading a host in place. Tokens need mesh:write to attach builtin Lua or WASM EnvoyExtensions or set xDS escape-hatch keys.
Nomad and HCP wrap-up. Nomad 2.0.7 allows wildcard namespace queries for native services. Vault 2.1 is rolling out to HCP Vault Dedicated clusters on AWS and Azure.
Fixed bufio.Scanner: token too long errors when logging requests or responses containing long lines.
BREAKING CHANGES:
cap_ipc_lock capability on vault at build time to allow running Vault in common container runtimes. Vault in containers will no longer be able to call mlock() to lock memory. Operators should set…Adds new resources and list resources for aws_cloudwatchomni_domain, aws_cloudwatchomni_space, aws_devopsagent_agent_space, aws_pricingplanmanager_subscription, and aws_cloudwatch_resource_metrics_configuration, plus resource identity support for aws_ram_principal_association and aws_ssm_service_setting and expanded arguments across CloudWatch, Bedrock, WAFv2, and RDS. Fixes include erroneous forced replacement on aws_ec2_transit_gateway_peering_attachment and a Read failure in aws_api_gateway_method.
Vault 2.1 has begun rolling out to HCP Vault Dedicated clusters on AWS and Azure, bringing the Vault 2.1.2 capabilities to HCP Vault.
Connect sidecar proxies and terminating gateways now receive leaf certificates and CA roots over SDS instead of inline in the listener filter chain, so leaf rotation no longer changes the filter chain hash and established connections (including long-lived TCP sessions) are not drained. Also fixes two proxycfg goroutine and memory leaks and restores Raft, Serf, and Memberlist metrics by building with the hashicorpmetrics tag.
Terraform Policy is now generally available, and the -policies flag for plan, apply, and query no longer requires an experimental build or the -allow-experimental-features flag. Also added the -minimal-refresh planning option, which refreshes only resources with proposed changes, and support for variables and locals in provider requirements.
Fixed a crash when a tainted instance state is seen without a valid status, and an issue where resource identity could be nil during delete.
The consul connect redirect-traffic command and transparent proxy redirection now use nftables instead of iptables/ip6tables, requiring the nft binary and Linux kernel 5.2 or later, with no automatic fallback; the official container image now ships nftables in place of iptables. API Gateway listeners also accept http2 and grpc protocols, enabling end-to-end HTTP/2 and gRPC instead of silently downgrading to HTTP/1.1.
Fixed bugs where namespaces and node pools could stop replicating between federated regions or be deleted in a follower region by an invalid replication token. Also fixes task restarts skipping shutdown_delay, image_pull_timeout not being respected past 5min, and unchanged jobs creating new versions when submitted with a different ACL token.
Updates github.com/apache/thrift to v0.24.0, golang.org/x/crypto to v0.56.0, and google.golang.org/grpc to v1.83.2 to fix ghsa-8wv5-x4w7-5gww, GO-2026-6354, GO-2026-6355, and GHSA-2v4p-qf9q-27wj. Also fixes auth/token/lookup returning 403 for JWT tokens in non-root namespaces, a panic in vault recover without a path, and OIDC identity token billing units computed incorrectly across periodic flush cycles.