Releases: cloudposse/build-harness
v0.57.4
🐛 Bug Fixes
Bugfix @Nuru (#285)
what
- Allow
validate_codeowners
to be triggered manually - Allow
cloudposse/contributors
to approve most Terraform changes - Fix bug where builder was referencing git SHA of project, not builder
why
- Bug in GitHub actions causes
validate_codeowners
to sometimes not run when it is supposed to - #277 inadvertently restricted
contributors
more than desired - #272 introduced a bug where the rule designed to ensure latest builder Docker image was being used would get the SHA of the wrong project and fail
v0.57.3
Adds auto-init capability using the bootstrap include directive @lorengordon (#272)
what
These changes will automatically run the make init
workflow, and keep the clone up-to-date with the target branch/tag.
why
-
People on my team kept forgetting to run
make init
, and it proved sufficiently frustrating (and often) that I figured I'd try to automate it. -
This makes it possible for the build-harness to update itself automatically. The user's Makefile can include
BUILD_HARNESS_BRANCH=<tag>
andBUILD_HARNESS_AUTO_INIT=true
, and they can have a mechanism that updates that tag value, and the auto-init logic will ensure that the checkout is updated automatically.
v0.57.2
v0.57.1
🐛 Bug Fixes
Remove generate-related-references target from auto-format @Nuru (#283)
what
- Remove
generate-related-references
target from auto-format added in #282
why
- Target cannot be built by currently deployed auto-format workflow
references
This version of auto-format.yaml
is currently deployed in nearly all Cloud Posse Terraform modules. It runs auto-format on build-harness:slim-latest
. The generate-related-references
requires Python 3 which is not installed in the slim image. We either need to abandon the idea of the slim image or deploy updated auto-format.yaml
that uses the full image to do auto-format.