v2.4.1

v2.4.1

This release includes an important bug fix that would prevent admins: <handle> from being able to deploy a change if no CI jobs were configured for a repo.

Additionally, more debug statements were added for troubleshooting issues

What's Changed

• Examples Documentation by @GrantBirki in #54
• Admin Deploy with Undefined CI checks by @GrantBirki in #55
• More Debug Usage by @GrantBirki in #56

Full Changelog: v2.4.0...v2.4.1

v2.4.0

v2.4.0

• Resolves a dependabot alert (#51)
• Updates documentation
• Updates usage guide
• Adds an extra log output statement for environment targets during the Actions run

---

• General Updates by @GrantBirki in #52

Full Changelog: v2.3.0...v2.4.0

v2.3.0

v2.3.0

This release introduces a fix for repos that do not have CI configured but still want to leverage branch deployments

What's Changed

• Empty CI Fix by @GrantBirki in #50

Full Changelog: v2.2.0...v2.3.0

v2.2.0

v2.2.0

The main change in this release is related to "Environment Target Fixes" as seen in this PR

This release fixes the way default environment targets work when no matching target is specified

Before

Before this change if you ran the following command .deploy to deevelopment, then the production env would be selected since no matching environments would be found due to the "development" typo. This is bad because a typo could cause a user to deploy to the wrong environment on accident

After

If the user mistypes an environment like the example above, then the user will get a warning that there is no matching deployment environment and the branch-deploy Action will exit.

---

What's Changed

• Environment Target Fixes by @GrantBirki in #46
• Stable Branch Fixes by @GrantBirki in #48

Full Changelog: v2.1.1...v2.2.0

v2.1.1

v2.1.1

Fixes a bug where the environment was not being set as an output by the Action

Full Changelog: v2.1.0...v2.1.1

v2.1.0

Environment Targets 🌍

This release now supports using environment targets with the branch deploy Action:

• .deploy to production
• .deploy development
• .deploy to development
• etc

See the linked PR below for full changes!

What's Changed

• Environment Targets 🌍 by @GrantBirki in #44

Full Changelog: v2.0.5...v2.1.0

v2.0.5

What's Changed

This release introduces a new admins: input as a feature! Check out the linked PR below to learn how it works

• Admins Feature 👩‍🔬 by @GrantBirki in #42

Full Changelog: v2.0.4...v2.0.5

v2.0.4

v2.0.4

This release fixes a bug that was introduced in patch v2.0.3 that would improperly deploy a branch if triggered from a fork

Full Changelog: v2.0.3...v2.0.4

v2.0.3

v2.0.3

A minor patch that adds the fork_full_name output for dealing with forks and pull requests with this Action

Full Changelog: v2.0.2...v2.0.3

v2.0.2

v2.0.2

This release enables a some additional output relating to repository forks. This will allow users to conditionally trigger workflows or behavior if a branch deploy initiates from a pull request that is from a fork

What's Changed

• Fork Outputs by @GrantBirki in #41

Full Changelog: v2.0.1...v2.0.2