v0.59.1

🐛 Bug Fixes

Only build build-harness from the build-harness project (bug in #299) @Nuru (#300)

what

• Only build build-harness from the build-harness project
• Fix comment about default Terraform version

why

• Bug in #299 causes Docker images to be built twice, the first time tagged with the build-harness Docker Image name and tag
• Inaccurate comment flagged in #299 but merged anyway

v0.59.0

Make 1.x the default Terraform version @Nuru (#299)

what

• Make 1.x the default Terraform version, replacing 0.13
• Add a build target to the Makefile

why

• When running the build-harness Docker image manually, tools usually use the default Terraform version, and this affects things like Terraform formatting. Cloud Posse is now using Terraform 1.x on all new projects, so it is a better default.
• The plain docker/build make target does not tag the Docker image with the tag other make targets expect to find, which makes developing build-harness unnecessarily difficult. Now make build will build and tag the image so that other commands like make build-harness/shell will find the image.

v0.58.4

Update AWS CLI @Nuru (#297)

what

• Update aws CLI to 1.20.28

why

• Needed to support EKS, specifically aws eks get-totken

v0.58.3

Create a draft release rather than no release with `no-release` label @Nuru (#296)

what

• When a PR is labeled no-release, still create a draft release

why

• Allows you to accumulate releases via the no-release tag and then make a manual release out of the draft release, taking advantage of the auto-releaser's drafting capabilities.

v0.58.2

Enable formatting of modules requiring TF 0.15 or TF 1.x @Nuru (#294)

what

• Enable formatting of modules requiring Terraform 0.15 or Terraform 1.x via make pr/auto-format etc.

why

• Auto format of modules requiring Terraform 0.15 or later was broken

v0.58.1

Add Terraform versions 0.15 and 1.x @Nuru (#293)

what

• Add Terraform versions 0.15 and 1.x

why

• Enable build and test with current versions of Terraform

v0.58.0

add conditional to related section or README template @mcalhoun (#290)

what

• Add a conditional around the related section of the readme template

why

• It is currently throwing an error when related is not present

{"level":"error","error":"template: /build-harness/templates/README.md.gotmpl:194:25: executing \"/build-harness/templates/README.md.gotmpl\" at <\"config\">: map has no entry for key \"related\"","time":"2021-05-14T17:04:06Z"}

v0.57.7

Better formatting of combined release notes @Nuru (#289)

what

• Preserve release note separate from Renovate Bot

why

• Makes release notes combined from several PRs more readable.

v0.57.6

Add support for "deprecated" flag/section in README @Nuru (#288)

what

• Add support for "deprecated" flag/section in README.yaml -> README.md
• Update auto-release workflow to run on push to other default branch names besides master

why

• Make it easy and consistent to mark a module as deprecated
• Allow us to use the same YAML file in all our repos as we change our default branch name

example

Add this to README.yaml

deprecated: 
  notice: |-
    This module is obsolete and has been replaced with [something else](link to something else)

or simply

deprecated: true

v0.57.5

Add `make` target to run pre-commit hooks @Nuru (#286)

what

• Add make target to run pre-commit hooks
• Update auto-release configuration with new Renovate bot PR format
• Update auto-readme to follow auto-format pattern
• Update Go 1.15.6 -> 1.15.11, closes #276
• Update Apline 3.12 -> 3.13, closes #275

why

• Pre-commit hooks are too heavyweight to require developers to install them, so give them a way to run them manually without installing them
• Renovate PR format changed, restore the ability of auto-release to remove irrelevant parts from Release Notes
• Fix README inside a PR rather than open a new PR, stop using obsolete set-env
• Stay current

editorial note

• My creation of this target should not be read as support for pre-commit hooks. I strongly prefer auto-format GitHub actions that do not impose any installation requirements on developers/contributors.