Releases: chrnorm/deployment-action
v2.0.7
What's Changed
- Fix dist files CI by @maks-oleksyuk in #86
New Contributors
- @maks-oleksyuk made their first contribution in #86
Full Changelog: v2.0.6...v2.0.7
v2.0.5
What's Changed
- fix deprecated set-output warnings by @piotrekkr in #74
New Contributors
- @piotrekkr made their first contribution in #74
Full Changelog: v2.0.4...v2.0.5
v2.0.4
What's Changed
- Fix: Creating deployments for another repository fails with
Not Found
by @liamoneill in #69
New Contributors
- @liamoneill made their first contribution in #69
Also, credit to @scotthogan for #66 which tackled the same problem in #69 (although I ended up merging #69 first). Thanks @scotthogan!
Full Changelog: v2.0.3...v2.0.4
v2.0.3
What's Changed
Full Changelog: v2.0.2...v2.0.3
v2.0.2
What's Changed
Full Changelog: v2.0.1...v2.0.2
v2.0.1
What's Changed
Full Changelog: v2...v2.0.1
v2.0.0
v2 of this action removes the target_url input and replaces it with the environment_url and log_url inputs to match GitHub's API. v2 also standardises on using kebab-case rather than snake_case for inputs to match GitHub's built-in actions.
Add optional `ref` parameter and improve the GitHub API call
The ref
parameter is a new optional parameter which allows a custom branch, tag, or SHA to be deployed.
- Fix: Add missing required attribute #17 (thanks to @localheinz)
- Enhancement: Allow specifying the actual reference #16 (thanks to @localheinz)
- fix target url #10 (thanks to @shallwefootball)
- use
environment_url
instead oftarget_url
#13
Fix for auto-merging and GitHub preview APIs
Rebuild lib/main.js
with the new auto_merge
parameter (was included in the previous release but wasn't actually compiled into the JS)
Add the preview APIs to the GitHub client initialization: const client = new github.GitHub(token, { previews: ["flash", "ant-man"] });
Control auto-merging of deployments
This release adds a new input parameter, auto_merge
, to the action. When set to "true"
, the action will attempt to auto-merge the default branch into the ref that the action is being ran on, as per the GitHub deployments documentation.
By default, auto_merge
is set to false
, which prevents GitHub attempting to auto-merge the default branch.
This should fix the intermittent deployment issues in #1 (thanks to @tiferrei for discovering the issue)