v1.1.1

What's Changed

• fix log name by @joshgubler in #24
• Bump hashicorp/setup-terraform from 2 to 3 by @dependabot in #23

Full Changelog: v1.1.0...v1.1.1

💥 Breaking 💥

For anything previously deployed, this will be a weird breaking change. terraform apply will probably fail to create the new log group because it already exists (the Lambda would have created it). If this happens to you, the solution is to use terraform import to link the correctly named log group in your terraform project's state file. Alternatively, you could delete the log group and let terraform create it, but this will be a race against any Lambda invocations.

(Yes, I know breaking changes should increment the major version number. But I couldn't bring myself to create v2.0.0 for such a simple bug fix)