v4.0.0

What's Changed

• Clarify alternate commands in README by @garnertb in #80
• Deployment Bug by @GrantBirki in #82
• Production Environment Feature by @GrantBirki in #83

📢 All users should upgrade to this release (v4.0.0) if possible as it fixes a critical bug where the deployment environment does not correctly get set when creating a new deployment. Many users who just use production were not impacted by this issue but all users who were using a unique production name (example: prod or prd) were impacted. This release contains fixes for this issue! 🎉 Huge thanks to @mwatson-x for discovering this bug in #81

This release also introduces a new optional input for the Action in #83 which allows users to specify a production_environment if the name is unique rather than just plain old production (examples: prod, prd, main, etc)

New Contributors

• @garnertb made their first contribution in #80

Full Changelog: v3.1.0...v4.0.0

v3.1.0

v3.1.0

The main changes of this release are:

• Fixes a bug where no status checks is set to success rather than null
• Adds a new GitHub Actions output that contains the deployment_id of the the deployment created by this Action

What's Changed

• add related lock Action notes by @GrantBirki in #69
• Clarify permissions in README by @tiagonbotelho in #75
• update documentation around permissions by @GrantBirki in #77
• fixing bug with no check statuses - should be set to null by @GrantBirki in #78
• Tiagonbotelho/expose deployment id output by @GrantBirki in #79

New Contributors

• @tiagonbotelho made their first contribution in #75

Full Changelog: v3.0.3...v3.1.0

v3.0.3

v3.0.3

This release updates the @actions/core library due to the deprecation of a few core methods

ref: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

What's Changed

• Update Actions Core by @GrantBirki in #65

Full Changelog: v3.0.2...v3.0.3

v3.0.2

v3.0.2

Bump ncc dependency version to the latest available

What's Changed

• Rollback Docs by @GrantBirki in #61
• bump ncc by @GrantBirki in #63

Full Changelog: v3.0.1...v3.0.2

v3.0.1

v3.0.1

A patch release to support an improved CI job

What's Changed

• add package-check by @GrantBirki in #59

Full Changelog: v3.0.0...v3.0.1

v3.0.0

v3.0.0

This release is a new major release as it changes the structure of the messages which the branch-deploy Action presents. This is a major change as it may break workflows that rely on the structure of these comments.

The majority of users should be able to use this version without any issues. Enjoy!

• #57

Examples 📸

Full Changelog: v2.4.1...v3.0.0

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