v2.1.0

chore: Option to Skip Atmos Functions @milldr (#48)

## what - Added `skip-atmos-functions` input

why

• When skip-atmos-functions is true, we can skip all atmos functions. This is necessary if we do not have AWS permission in GH actions

references

• cloudposse/github-action-atmos-affected-stacks#60

Update spacelift-io/setup-spacectl action to v1 @[renovate[bot]](https://github.com/apps/renovate) (#35)

This PR contains the following updates:

Package	Type	Update	Change
spacelift-io/setup-spacectl	action	major	v0.10.0 -> v1.0.0

---

Release Notes

spacelift-io/setup-spacectl (spacelift-io/setup-spacectl)

v1.0.0

Compare Source

What's Changed

• Remove the need for specifying GITHUB_TOKEN env by @​peterdeme in https://github.com/spacelift-io/setup-spacectl/pull/18

Full Changelog: spacelift-io/setup-spacectl@v0.10.0...v1.0.0

---

🤖 Automatic Updates

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

## 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 (#42)

## 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 (#41)

## 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 (#39)

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

why

• Support new readme generation workflow.
• Generate banners

v2.0.1

Update spacelift-io/setup-spacectl action to v0.10.0 @renovate (#34)

This PR contains the following updates:

Package	Type	Update	Change
spacelift-io/setup-spacectl	action	minor	v0.9.0 -> v0.10.0

---

Release Notes

spacelift-io/setup-spacectl (spacelift-io/setup-spacectl)

v0.10.0

Compare Source

What's Changed

• Bump node packages by @​peterdeme in https://github.com/spacelift-io/setup-spacectl/pull/17

Full Changelog: spacelift-io/setup-spacectl@v0.9.0...v0.10.0

---

Update marocchino/sticky-pull-request-comment action to v2.9.0 @renovate (#33)

This PR contains the following updates:

Package	Type	Update	Change
marocchino/sticky-pull-request-comment	action	minor	v2.8.0 -> v2.9.0

---

Release Notes

marocchino/sticky-pull-request-comment (marocchino/sticky-pull-request-comment)

v2.9.0

Compare Source

• Update deps
• Use node 20

---

Update spacelift-io/setup-spacectl action to v0.9.0 @renovate (#28)

This PR contains the following updates:

Package	Type	Update	Change
spacelift-io/setup-spacectl	action	minor	v0.4.0 -> v0.9.0

---

Release Notes

spacelift-io/setup-spacectl (spacelift-io/setup-spacectl)

v0.9.0

Compare Source

What's Changed

• Bump indirect dependencies by @​peterdeme in https://github.com/spacelift-io/setup-spacectl/pull/15

Full Changelog: spacelift-io/setup-spacectl@v0.8.0...v0.9.0

v0.8.0

Compare Source

What's Changed

• Bump packages, update README about deprecated env var by @​peterdeme in https://github.com/spacelift-io/setup-spacectl/pull/14

Full Changelog: spacelift-io/setup-spacectl@v0.7.0...v0.8.0

v0.7.0

Compare Source

What's Changed

• chore: bump indirect packages by @​peterdeme in https://github.com/spacelift-io/setup-spacectl/pull/12

Full Changelog: spacelift-io/setup-spacectl@v0.6.0...v0.7.0

v0.6.0

Compare Source

What's Changed

• Bump indirect dependencies by @​peterdeme in https://github.com/spacelift-io/setup-spacectl/pull/11

Full Changelog: spacelift-io/setup-spacectl@v0.5.0...v0.6.0

v0.5.0

Compare Source

What's Changed

• Set to node20 and bump packages by @​peterdeme in https://github.com/spacelift-io/setup-spacectl/pull/9

Full Changelog: spacelift-io/setup-spacectl@v0.4.0...v0.5.0

---

Update actions/checkout action to v4 @renovate (#27)

This PR contains the following updates:

Package	Type	Update	Change
actions/checkout	action	major	v3 -> v4

---

Release Notes

actions/checkout (actions/checkout)

v4

Compare Source

• Support fetching without the --progress option
• Update to node20

---

Update marocchino/sticky-pull-request-comment action to v2.8.0 @renovate (#25)

This PR contains the following updates:

Package	Type	Update	Change
marocchino/sticky-pull-request-comment	action	minor	v2.6.2 -> v2.8.0

---

Release Notes

marocchino/sticky-pull-request-comment (marocchino/sticky-pull-request-comment)

v2.8.0

Compare Source

• Add skip_unchanged input
• Update deps

v2.7.0

Compare Source

Update deps.
Add two output.

• previous_comment_id: "ID of previous comment, if found"
• created_comment_id: "ID of newly created comment, if any"

---

🤖 Automatic Updates

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

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

v2.0.0

add pattern matching fix @mcalhoun (#26)

what

Update the order of comments from /spacelift {preview,deploy} [stackname] to /spacelift [stackname] {preview,deploy}

why

When there are stacks whose ids are substrings of other stacks, both stacks were accidentally triggered because the spacelift policy uses contains(input.pull_request.comment, concat(" ", ["/spacelift", "preview", input.stack.id])) to match the comments from the Pull Request.

references

cloudposse/terraform-spacelift-cloud-infrastructure-automation PR

v1.3.0

add atmos-include-spacelift-admin-stacks variable @mcalhoun (#24)

what

Add the atmos-include-spacelift-admin-stacks variable when calling github-action-atmos-affected-stacks

why

To also include the affected admin stacks

v1.2.2

🚀 Enhancements

fix comments @mcalhoun (#23)

what

Add /spacelift summary to the beginning of the comment as a hack so that spacelift will evaluate the comment

why

Currently, spacelift will only evaluate the comment event from github if the comment begins with /spacelift per the documentation:

Please note that Spacelift will only evaluate comments that begin with/spacelift to prevent users 
from unintended actions against their resources managed by Spacelift. Furthermore, Spacelift only 
processes event data for new comments, and will not receive event data for edited or deleted comments.

references

• Spacelift Docs

🐛 Bug Fixes

fix comments @mcalhoun (#23)

what

Add /spacelift summary to the beginning of the comment as a hack so that spacelift will evaluate the comment

why

Currently, spacelift will only evaluate the comment event from github if the comment begins with /spacelift per the documentation:

Please note that Spacelift will only evaluate comments that begin with/spacelift to prevent users 
from unintended actions against their resources managed by Spacelift. Furthermore, Spacelift only 
processes event data for new comments, and will not receive event data for edited or deleted comments.

references

• Spacelift Docs

v1.2.1

🚀 Enhancements

Chore/pin to major release tag @mcalhoun (#22)

what

• Pin the version of github-action-atmos-affected-stacks to v1 instead of a specific version

why

• To allow us to use the latest version of v1 each time it's released

v1.2.0

Fix Comment Body @milldr (#21)

what

• check for empty comment before running the comment action
• correct comment body within collapsed block

why

• If the only affected stacks have settings.spacelift.workspace_enabled: false, then the comment body will be empty. If the comment body is empty, then the actions fails:

Error: Either message or path input is required

• The comment body was not formatted correctly when inside a collapsed block

references

• n/a

v1.1.0

wrap comments in details block @mcalhoun (#20)

what

• Wrap the comments in a details block

why

• So that stacks with large numbers of affected stacks don't take up a lot of screen real estate on the PR by default

references

Supercedes #19. Thanks to @MaxymVlasov for the contribution!

Update cloudposse/github-action-atmos-affected-stacks action to v1.0.2 @renovate (#18)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/github-action-atmos-affected-stacks	action	patch	1.0.1 -> 1.0.2

---

Release Notes

cloudposse/github-action-atmos-affected-stacks

v1.0.2

Compare Source

Added major release tagger @​zdmytriv (#​13)

what

• Added major release tagger github action that will manager v tags.

why

• Added major release tagger github action that will manager v tags.

references

• https://github.com/cloudposse/github-action-major-release-tagger

🤖 Automatic Updates

Update README.md and docs @​cloudpossebot (#​9)

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

---

v1.0.1

Added major release tagger (#17)

* Added major release tagger

* update

v1.0.0

support using comments for triggering @mcalhoun (#12)

what

Add the ability for GHA to trigger atmos affected stacks via comments/push policy

why

• Provides a way to trigger only the atmos affected stacks while keeping the ability to still use spacelift policies to trigger runs, cancel jobs, etc.

references

• https://docs.spacelift.io/concepts/run/pull-request-comments
• https://github.com/spacelift-io/spacelift-policies-example-library/blob/main/push/pr-comment-driven-actions.rego