Skip to content

Releases: github/branch-deploy

v4.5.2

07 Mar 15:06
c2a6b34

Choose a tag to compare

v4.5.2

What's Changed

Full Changelog: v4.5.1...v4.5.2

v4.5.1

06 Mar 21:22
5b490fd

Choose a tag to compare

v4.5.1

Adding better support for users on GHES by using environment variables to find the GitHub server URL rather than hardcoding https://github.com

What's Changed

Special Thanks

Thanks to @KevinMSampson for raising attention around GHES support.

Full Changelog: v4.5.0...v4.5.1

v4.5.0

02 Mar 11:25
0c7c257

Choose a tag to compare

v4.5.0

What's Changed

Full Changelog: v4.4.1...v4.5.0

v4.4.1

02 Mar 10:09
d182017

Choose a tag to compare

v4.4.1

What's Changed

Full Changelog: v4.4.0...v4.4.1

v4.4.0

27 Feb 11:20
cddb02d

Choose a tag to compare

v4.4.0

This release adds a new Action's input option (skip_completing) that allows for manual control of when and how deployment status are set by the user. This is an advanced option but will allow for further flexibility when using this Action.

What's Changed

New Contributors

Full Changelog: v4.3.0...v4.4.0

v4.3.0

15 Feb 14:48
e0b8fec

Choose a tag to compare

v4.3.0

Adds the .help command to the Action 🎉

The help command uses your Action's configuration to generate a dynamic help command output directly on your pull request so contributors know how to operate deployments through IssueOps.

What's Changed

Full Changelog: v4.2.1...v4.3.0

v4.2.1

15 Feb 12:08
4c16773

Choose a tag to compare

v4.2.1 Pre-release
Pre-release

v4.2.1

What's Changed

Full Changelog: v4.2.0...v4.2.1

v4.2.0

13 Feb 16:23
e76bfe3

Choose a tag to compare

v4.2.0 Pre-release
Pre-release

v4.2.0

What's Changed

Full Changelog: v4.1.0...v4.2.0

v4.1.0

01 Feb 22:06
59cb87c

Choose a tag to compare

v4.1.0

What's Changed

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

v4.0.0

02 Jan 05:36
3139980

Choose a tag to compare

What's Changed

📢 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

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