v2.0.1

Latest points to most recent stable release @Benbentwo (#100)

## what * Initial Tests * Disables fetching pre-releases (Release candidates) when pointing to latest

why

• Latest should point at the latest stable release

docs: update version -> atmos-version @westonplatter (#99)

## what * have example match `input` specification

Update README @goruha (#76)

## what * Update `cloudposse/github-action-setup-atmos@v1` to `cloudposse/github-action-setup-atmos@v2` in README

why

• To use the latest version in example

🤖 Automatic Updates

Update .github/settings.yml @osterman (#96)

## what - Update `.github/settings.yml` - Drop `.github/auto-release.yml` files

why

• Re-apply .github/settings.yml from org level
• Use organization level auto-release settings

references

• DEV-1242 Add protected tags with Repository Rulesets on GitHub

Update release workflow to allow pull-requests: write @osterman (#92)

## what - Update workflow (`.github/workflows/release.yaml`) to have permission to comment on PR

why

• Add comment to PR when it is released

Use GitHub Action Workflows from `cloudposse/.github` Repo @osterman (#90)

## what - Update workflows (`.github/workflows/settings.yaml`) to use shared workflows from `.github` repo

why

• Reduce nested levels of reusable workflows

Use GitHub Action Workflows from `cloudposse/.github` Repo @osterman (#84)

## what - Update workflows (`.github/workflows/settings.yaml`)

why

• Support new readme generation workflow.
• Generate banners

Update README.md and docs @cloudpossebot (#72)

## what This is an auto-generated PR that updates the README.md and docs

why

To have most recent changes of README.md and doc from origin templates