v1.31.1

Docker build fixes @Nuru (#369)

what

• Update tool versions
• Force Docker build platform linux/amd64
• Update docker and vhs workflows to use Node v20 actions
• Add concurrency check to docker workflow

why

• Stay current with features and bugfixes
• Docker image is based on Alpine, and Cloud Posse packages for Alpine are only available for amd64 (no ARM support)
• Node 16 is deprecated
• Cancel builds that are superseded

Update template with support for .github/banner.png @osterman (#367)

what

• Update readme to display banner, if available
• Add a banner

why

• Spruce up our repos

relates to

• cloudposse/.github#20

🐛 Bug Fixes

Properly scope Docker build flags for build-harness project @Nuru (#370)

what

• Scope default setting of DOCKER_BUILD_FLAGS to the build-harness project only

why

• Bug introduced in #369: Setting DOCKER_BUILD_FLAGS where it did affects all projects using build-harness, which includes most people's custom Geodesic images. It was intended to only affect the build of build-harness images.

v1.31.1-rc1

Update template with support for .github/banner.png @osterman (#367)

what

• Update readme to display banner, if available
• Add a banner

why

• Spruce up our repos

relates to

• cloudposse/.github#20

v1.31.0

Remove warning about Gnu `make` version @Nuru (#366)

what

• Remove warning about Gnu make version added in #360

why

• The warning was unnecessary, misleading, and overly specific
  • The warning checked for "GNU Make 4.4". This of course will break when version 4.5 comes out. Furthermore, Ubuntu 20.4 LTS currently has GNU Make 4.2, which also triggers the warnings
  • The issues with building on macOS that were purported to be fixed by using GNU Make have not been clearly connected to the make version. I strongly suspect any issues with builds on Mac to be related to such things as macOS shipping with the ancient bash version 3.2.57, which is missing important features available in the current bash v5, or other aspects of macOS deviations from POSIX. These should be addressed by fixing the broken build recipes, not by requiring action on the part of the user (unless action is required, like installing jq, in which case this should cause an explicit and specific error message to be generated.

Move screenshots above banners @osterman (#365)

what

• Move screenshots above banners

why

• Move more important things above the fold

references

v1.30.0

Update readme formatting @osterman (#363)

what

• Reduce header size
• Reorganize content, especially cloud posse branding
• Update demo gif with automation (VHS)
• Use admonitions
• 

why

• Promote more content above-the-fold

v1.29.0

Rebuild README @milldr (#362)

what

• Rebuild the README for this repo using the latest template

why

• The template has been updated with #361
• Previously, the auto-readme check would overwrite this readme

references

• #361

v1.28.0

Readme Improvements @milldr (#361)

what

• Update README template with latest preferences
• Do not run auto-readme if modules/readme label
• Change auto-readme to trigger on pull_request

why

• Remove unnecessary sections and reorganize README template that is used to populate all cloud posse repos
• Update the README with the PR intentionally
• pull_request_target does not support labels; pull_request does.

references

• https://github.com/orgs/community/discussions/14407

v1.27.0

Warning for make version @max-lobur (#360)

what

Warn on make version mismatch
It's just a warning message, intentionally not adding exit 1 to see how it goes.

why

We've had numerous issues with built-in macos make. Let's warn users if their version doesn't match what we expect

Regenerate README @milldr (#359)

what

• Regenerate README

why

• Regenerated with the latest go template for READMEs

references

• #358

v1.26.0

README Template Update @milldr (#358)

what

• Replaced Contributors with contrib.rocks contributors block
• Removed social links and discourse
• Clean up unnecessary content

why

• Automatically keep contributors up-to-date
• Our contributors are gravely out of date
• It helps to showcase the popularity of a repo
• Keeping README up-to-date with latest conventions/recommendations

references

• Internal discussion: https://github.com/cloudposse/knowledge-base/discussions/161

v1.25.0

🐛 Bug Fixes

Handle spaces in path to Docker command @Nuru (#357)

what

• Handle the case where the path to the docker command has a space in it
• Update dependencies
  • Alpine 3.17 -> 3.18
  • Go 1.20.4 -> 1.20.7
  • tflint AWS ruleset 0.23.0 -> 0.26.0
  • Python packages:
    • cryptography 41.0.2 -> 41.0.3
    • awscli 1.29.9 -> 1.29.25
    • boto3 1.28.9 -> 1.28.25
    • PyGithub 1.59 -> 1.59.1
  • lint.yml workflow:
    • cloudposse/build-harness 1.8.0 -> latest
    • actions/checkout v2 -> v3
    • github/super-linter/slim v4 -> v5

why

• On macOS, some standard directories (e.g. "Application Support") have spaces in them
• Keep current with security patches and bug fixes

references

• Fixes #356

Note that make, and therefore build-harness, does not generally support spaces in path names. In particular, build-harness will not be extended to support spaces in the path to the build-harness installation or the current working directory.

v1.24.0

Update pre-commit to run pre-push @Nuru (#355)

what

• Update make targets pr/pre-commit and pre-commit/run to only run the pre-push stage of pre-commit
• Update Python package versions
• Update Docker GitHub actions

why

• Target is intended to be used pre-push, and previous target ran against all files, which both took excessively long and sometimes made unwanted changes to large numbers of untouched files.
• PyYaml 5.4.1 no longer installs because of Cython v3, + bug and security fixes
• Migrate away from deprecated features

references

• yaml/pyyaml#724