Releases: cloudposse/build-harness
Releases · cloudposse/build-harness
v1.0.1
v1.0.0 Initial release with production Semantic Versioning
Initial release with production Semantic Versioning, part of Cloud Posse's general policy to convert to production versioning as we make updates to relatively mature code.
v0.62.3
🐛 Bug Fixes
GitHub action updates @Nuru (#313)
what
- Possible workaround for actions/checkout#766
- Additional logging when updating GitHub action workflows
- Update
go
1.17.7 -> 1.17.9
why
- Fix breaking
auto-format
in Cloud Posse Terraform repos - More readable output
- Security fixes
v0.62.2
🐛 Bug Fixes
Auto-readme workflow fix: name of default branch rather than hard coding it @Nuru (#312)
what
- Fix
auto-readme
workflow to detect the name of the default branch rather than rely on hard codedmain
- Only output the message "Ignoring whitespace-only changes in README" when, in fact, there are changes to ignore
why
- Most of our repos still use
master
for the default branch, but some usemain
and we need the right target for the PR this workflow creates - It was confusing to see that message when there were, in fact, no changes at all
v0.62.1
v0.62.0
GitHub auto update @Nuru (#310)
what
- Update GitHub workflows as part of make pr/auto-format
- Update
codeowners-validator
to current version 0.7.1 - Update Go 1.15.11 -> 1.17.7, Alpine 3.13 -> 3.15
why
- Keep modules up-to-date without triggering massive waves of PRs that require high-level approvals
- Version 0.5.0 stopped working
- Security fixes
v0.61.1
🐛 Bug Fixes
Update validate codeowners, install auto-readme @Nuru (#309)
what
- Mark Terraform
get-plugins
andget-modules
as Obsolete - Automatically install
auto-readme.yml
workflow in Terraform modules - Update
codeowners-validator
from v0.5.0 -> v0.6.0 - Fix
make terraform/get-plugins
andmake clean
, thanks to @jbouse - Fix
make/help
andmake help/all
, thanks to @slewis-bd - Update
super-linter
to v4
why
- No longer supported by Terraform
- Cause changes to README template to propagate to all modules without creating a new release
- Multiple bug fixes in
codeowners-validator
- Closes #305, supersedes and closes #306
- Closes #307
- Super Linter v3 has known issues and security flaws and is considered obsolete
references
v0.61.0
v0.60.0
v0.59.2
🐛 Bug Fixes
Finish #299, default to Terraform v1 in builder-slim @Nuru (#302)
what
- Finish #299, default to Terraform v1 in builder-slim
- Symlink current Terraform
major
.minor
directories tomajor
- Fix bash test. Thanks @tevansuk
- Support
no-release
label
why
- #299 Made Terraform 1.x for the
builder
Docker image but neglected to update thebuilder-slim
Docker image. - Some deployed Makefiles expect Terraform to be installed in a directory named with
major
.minor
due to pre-production versions using semver0.major
versioning. With Terraform production version, the major version is back to its rightful place, so we only needmajor
, but the old Makefile are installed in hundreds of Terraform modules, so we need some backward support for them. - Bad syntax in Makefile causes errors during auto-init.
- Sometimes we want to merge changes (such as for PR #298) without triggering a release, for example to bundle several PRs into a single release.