chore(deps): update suzuki-shunsuke/lock-action action to v0.1.5

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
suzuki-shunsuke/lock-action	action	patch	v0.1.1 -> v0.1.5

---

Release Notes

suzuki-shunsuke/lock-action (suzuki-shunsuke/lock-action)

v0.1.5

Compare Source

Issues | Pull Requests | suzuki-shunsuke/lock-action@v0.1.4...v0.1.5 | Base revision

Others

#​158 ci: Sign commits and tags when releasing

We automate the release by script and CI.
We can release a new version by cmdx r command.

e.g.

cmdx r v0.1.4

Release commits and tags were created by CI, but they weren't signed.

e.g.

https://github.com/suzuki-shunsuke/lock-action/releases/tag/v0.1.5

As of this release, we improved the release flow and we could sign commits and tags, which making this action more reliable.

https://github.com/suzuki-shunsuke/lock-action/releases/tag/v0.1.5

v0.1.4

Compare Source

Issues | Pull Requests | suzuki-shunsuke/lock-action@v0.1.3...v0.1.4 | Base revision

Features

#​135 Add an output locked if mode is either lock or check

This output is useful for other GitHub Actions jobs to check if the job acquires the lock.

e.g.

  lock:
    runs-on: ubuntu-latest
    permissions:
      contents: write
    outputs:
      locked: ${{steps.lock.outputs.locked}}
    steps:
      - uses: suzuki-shunsuke/lock-action@c752be910ac812e0adc50316855416514d364b57 # v0.1.3
        id: lock
        with:
          mode: lock
          key: dev

##### ...

  unlock:
    runs-on: ubuntu-latest
    needs: lock
    permissions:
      contents: write
    steps:
      - uses: suzuki-shunsuke/lock-action@c752be910ac812e0adc50316855416514d364b57 # v0.1.3
        if: needs.lock.outputs.locked == 'true'
        with:
          mode: unlock
          key: dev

v0.1.3

Compare Source

Issues | Pull Requests | suzuki-shunsuke/lock-action@v0.1.2...v0.1.3 | Base revision

Features

#​73 Add the input fail_if_locked

The input fail_if_locked has been added.
This input is for mode: check.

e.g.

- uses: suzuki-shunsuke/lock-action@latest
  with:
    mode: check
    key: foo
    fail_if_locked: "true"

By default, this input is false.
If this input is true and the given key is being locked, the step fails.

v0.1.2

Compare Source

Issues | Pull Requests | suzuki-shunsuke/lock-action@v0.1.1...v0.1.2 | Base revision

Features

#​18 #​70 Support retrying until a lock is released

Inputs max_wait_seconds and wait_interval_seconds have been added.
By default max_wait_seconds is 0 and this action doesn't retry.
Modes lock and check support these inputs.

If the mode is lock and max_wait_seconds is greater than 0, this action retries to acquire the lock every wait_interval_seconds until max_wait_seconds.

If the mode is check and max_wait_seconds is greater than 0, this action retries to check the lock every wait_interval_seconds until max_wait_seconds.

1. check

- uses: suzuki-shunsuke/[email protected]
  id: check
  with:
    mode: check
    key: default
    max_wait_seconds: "60"
    wait_interval_seconds: "10"

2. lock

- uses: suzuki-shunsuke/[email protected]
  with:
    mode: lock
    key: default
    max_wait_seconds: "60"
    wait_interval_seconds: "10"

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.