Skip to content

chore(deps)(deps): bump lewagon/wait-on-check-action from 1.5.0 to 1.8.0#10

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/lewagon/wait-on-check-action-1.8.0
Open

chore(deps)(deps): bump lewagon/wait-on-check-action from 1.5.0 to 1.8.0#10
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/lewagon/wait-on-check-action-1.8.0

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jun 11, 2026

Copy link
Copy Markdown

Bumps lewagon/wait-on-check-action from 1.5.0 to 1.8.0.

Release notes

Sourced from lewagon/wait-on-check-action's releases.

v1.8.0

Added

  • Add a wait-for-duplicates option to require every check with a duplicate name to succeed (#154)

v1.7.0

Fixed

  • Fix the failure exit codes (#147)

v1.6.1

Added

  • Pin the ruby/setup-ruby version (#143)

v1.6.0

Added

  • Add checks-discovery-timeout option (#139)
Changelog

Sourced from lewagon/wait-on-check-action's changelog.

v1.8.0 - 2026-06-09

Added

  • Add a wait-for-duplicates option to require every check with a duplicate name to succeed

v1.7.0 - 2026-04-14

Fixed

  • Fix the failure exit codes

v1.6.1 - 2026-04-06

Added

  • Pin the ruby/setup-ruby version

v1.6.0 - 2026-03-29

Added

  • Add checks-discovery-timeout option
Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [lewagon/wait-on-check-action](https://github.com/lewagon/wait-on-check-action) from 1.5.0 to 1.8.0.
- [Release notes](https://github.com/lewagon/wait-on-check-action/releases)
- [Changelog](https://github.com/lewagon/wait-on-check-action/blob/master/CHANGELOG.md)
- [Commits](lewagon/wait-on-check-action@v1.5.0...v1.8.0)

---
updated-dependencies:
- dependency-name: lewagon/wait-on-check-action
  dependency-version: 1.8.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot @github

dependabot Bot commented on behalf of github Jun 11, 2026

Copy link
Copy Markdown
Author

Labels

The following labels could not be found: dependencies, github-actions. Please create them before Dependabot can add them to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

@dependabot dependabot Bot requested a review from bniladridas as a code owner June 11, 2026 21:13
@vesper-review

vesper-review Bot commented Jun 11, 2026

Copy link
Copy Markdown
Vesper

Reviewed commits

Commit Summary
61883cb chore(deps)(deps): bump lewagon/wait-on-check-action from 1.5.0 to 1.8.0

The proposed change updates the lewagon/wait-on-check-action from version v1.5.0 to v1.8.0.

Analysis

  • Correctness & Performance: The update is correct and brings in bug fixes and improvements from the newer version of the action.
  • Security: As a general security best practice for GitHub Actions, pinning third-party actions to a specific commit SHA (rather than a mutable tag like v1.8.0) prevents potential supply chain attacks if the tag is ever maliciously reassigned.

Since the update itself is correct and standard, the change is good to merge. If you wish to harden the security of this workflow, you can pin the action to its specific commit SHA.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants