Release v1!20230822.175356

chore: update dependencies

Release v1!20220215.164420

feat: add support for Rules section in templates

Release v1!20210428.135057

Allow CloudFormation !Expressions to be merged

... as long as they're the same expression.

Release v1!20210428.135003

Bump pyyaml from 5.1 to 5.4

Bumps [pyyaml](https://github.com/yaml/pyyaml) from 5.1 to 5.4.
- [Release notes](https://github.com/yaml/pyyaml/releases)
- [Changelog](https://github.com/yaml/pyyaml/blob/master/CHANGES)
- [Commits](https://github.com/yaml/pyyaml/compare/5.1...5.4)

Signed-off-by: dependabot[bot] <[email protected]>

Release v1!20210320.41904

Bump jinja2 from 2.10.1 to 2.11.3

Bumps [jinja2](https://github.com/pallets/jinja) from 2.10.1 to 2.11.3.
- [Release notes](https://github.com/pallets/jinja/releases)
- [Changelog](https://github.com/pallets/jinja/blob/master/CHANGES.rst)
- [Commits](https://github.com/pallets/jinja/compare/2.10.1...2.11.3)

Signed-off-by: dependabot[bot] <[email protected]>

Release v1!20200723.161030

Make linter happy

- E501 line too long (156 > 100 characters)
- F523 '...'.format(...) has unused arguments at position(s): 2
- F541 f-string is missing placeholders

Release v1!20200417.104641

Allow stack names to be overridden

The schema for a stack already contemplated a name field, but it was
entirely ignored, otherwise.

The main use case for overriding a stack name, is to give some
flexibility when adopting legacy stacks. Allowing stacks to be mapped
into a stack/legacy/{account}/{stack-name}.yaml structure while taking over
the existing stack's name and template.

(Otherwise, while the stack/{account}/{stack-name}.yaml structure looks
clean, it does not encourage template reuse across accounts, and makes
it harder to spot differences between corresponding stacks.)

Release v1!20200113.95235

Convert booleans in stack parameters to 'true'/'false'

Release v1!20200113.94032

Remove debug output accidentally introduced in f2cedf04

Release v1!20200112.102009

Github Actions are awesome

Adds a publish job to the CI workflow. It run on successful `master`
builds to automatically release and publish packages as Github Release
and to PyPI.

The intent is to automatically publish anything pushed to the master
branch, to keep project/release management overhead low for now.