$ the-wire · showcase
Consul gates localized DNS behind a feature flag, metadata action learns multi-product repos
By RepoJournal · Filed · About HashiCorp · Composed from the cited sources · methodology
2 people shipped this
Consul's localized DNS work landed under a feature gate that ends up enabled by default, while the metadata generation action gained multi-product repository support and shipped v1.3.0.
Dns feature gate (#23935) hashicorp/consul
Consul's localized DNS now sits behind a feature gate, though the same change enables it by default and turns it on in tests, and it also skips the resolver check on the Consul client. Operators who want the old resolution path should confirm the gate's behavior in their config before assuming it is opt-in.
v1.3.0 - Multi-Product Repository Support hashicorp/actions-generate-metadata
actions-generate-metadata v1.3.0 adds a `releaseSubDir` input so a single repository can build multiple products, auto-deriving both `security-scan.hcl` and `release-metadata.hcl` paths from it. The new `release_sub_dir` field in metadata.json is omitted when empty, so existing single-product pipelines keep working; the action's own notes call the path resolution fixed.
fix: auto-derive release-metadata.hcl path from releaseSubDir hashicorp/actions-generate-metadata
The underlying fix resolves `release-metadata.hcl` as `.release/<releaseSubDir>/release-metadata.hcl` instead of hardcoding `.release/release-metadata.hcl`. Previously the `releaseMetadata` field in metadata.json came back empty and the action emitted a "Missing release metadata" warning for multi-product repos.
Merge pull request #127 from hashicorp/release-v2.3.0 hashicorp/actions-docker-build
The Docker build action tagged v2.3.0, the desk's routine release of the day. Nothing in the change set signals a migration for consumers of the action.
