Skip to content

Releases: cloudposse/build-harness

v0.57.4

05 Apr 23:38
54e8f69
Compare
Choose a tag to compare

🐛 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

22 Mar 21:37
d1e31d6
Compare
Choose a tag to compare
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

  1. 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.

  2. This makes it possible for the build-harness to update itself automatically. The user's Makefile can include BUILD_HARNESS_BRANCH=<tag> and BUILD_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

28 Feb 03:04
9b3f579
Compare
Choose a tag to compare
auto-release respect 'no-release' label @maximmi (#279)

what

  • auto-release respect 'no-release' label

why

  • to be able to avoid publishing a release when one is not needed (ex. when only readme/docs was updated)

v0.57.1

23 Feb 23:54
5e28800
Compare
Choose a tag to compare

🐛 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.

v0.57.0

23 Feb 13:15
1706ebf
Compare
Choose a tag to compare
integration of generate-related-references target @maximmi (#282)

what

  • target to generate related and references sections to README.yaml integrated into auto-format workflow

why

  • to have up to date related and references sections in README.md on each PR update

v0.56.0

19 Feb 17:38
621faa8
Compare
Choose a tag to compare
nightly build added @maximmi (#281)

what

  • nightly docker build with tags latest and nightly

why

  • build added before midnight to prepare build-harness images before most of nightly build fires

v0.55.0

13 Feb 01:57
065abd3
Compare
Choose a tag to compare
mergify rule to close PRs without changes @maximmi (#280)

what

  • Mergify rule to close PRs without changes

why

  • To avoid unnecessary pushes to master branch

v0.54.0

04 Feb 14:44
3349fb5
Compare
Choose a tag to compare
approvers now allowed to review all *.tf files @maximmi (#277)

what

  • approvers now allowed to review all *.tf files

why

  • we have not given Mergify permission to merge changes to the .tf files. So all the Renovate PRs will require manual approval.

v0.53.0

02 Feb 05:40
4cae2fa
Compare
Choose a tag to compare
Update README.md Template with BridgeCrew Compliance Badges @maximmi (#256)

what

  • README.md Template updated with BridgeCrew Compliance Badges

why

  • To be able see and fix the recommendations from Bridgecrew so we can position our modules as standards compliant

v0.52.0

28 Jan 19:51
563d373
Compare
Choose a tag to compare
feat: add dynamic update the list of related references @SweetOps (#273)

what

  • add script that will dynamically update the list of related references in the README.yaml

references

  • CPCO-361