v1.5.0

v1.5.0

The main feature of this release is allowing users to have an option when it comes to "up-to-date" branch requirements for deployments. For certain situations, it is not desirable to allow users to trigger branch-deployments if a branch is not "up-to-date" with the target branch.

This release now allows users to set a new input parameter when installing this action: update_branch

This new input parameter can have three different values:

• disabled - The action will not take the state of the branch into consideration when doing deployments
• warn - This is the suggested option. It will exit the workflow and leave a warning comment on the pull request which initiated the workflow. It will tell the user that the branch must be updated in order for a deploy/noop to continue
• force - This option is not suggested due to GitHub Action preventing recursive workflow runs from merge commits that are triggered by other workflows. This option will have the Action force update the branch for you

The default option for this new input parameter is warn and will default to this value if nothing is set

What's Changed

• Enforce Updated Branches (noop mode) by @GrantBirki in #27
• Strict update fixes by @GrantBirki in #28
• update_branch param by @GrantBirki in #29

Full Changelog: v1.4.2...v1.5.0