v7.5.0

v7.5.0

@hubot Style Deploy Locking 🔒

This release introduces Hubot Style Deploy Locking (aka sticky deployment locks). Currently, when you run .deploy it creates a lock during the deployment and then releases the lock when the deployment completes. By using the new input option that this release introduces, you can change the deployment locking behavior so that the lock persists even after the deployment finishes.

New Input Options:

• sticky_locks - By default, this value is set to "false".
• sticky_locks_for_noop - By default, this value is set to "false". You should probably leave it disabled unless you have a significant reason to lock an environment due to a .noop style deployment

Example:

- name: branch-deploy
  id: branch-deploy
  uses: github/[email protected]
    with:
      sticky_locks: "true" # <--- enables sticky deployment lock / hubot style deployment locks
      sticky_locks_for_noop: "true" # <--- enables sticky deployment lock / hubot style deployment locks for noop deployments
      # ... other configuration

This option, combined with the "Unlock on Merge" workflow strategy is highly suggested for mission critical projects using this Action to deploy their code to production.

You can learn more about this new method of deployment locking by reading the new documentation 📚.

This release will be internally tested at GitHub before being set to the latest release

What's Changed v7.4.0

• add base_ref output by @GrantBirki in #194
• update docs by @GrantBirki in #197
• Hubot Style Deploy Locking 🔒 by @GrantBirki in #199
• Update docs by @GrantBirki in #200

Full Changelog: v7.3.1...v7.4.0

What's Changed v7.5.0

• Sticky Locks for noop deployments by @GrantBirki in #202

Full Changelog: v7.4.0...v7.5.0