New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update dependency spectron to v19 #92

Open

renovate wants to merge 1 commit into master from renovate/spectron-19.x

renovate bot commented Mar 25, 2023 •

edited

Loading

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
spectron	`3.8.0` -> `19.0.0`

Release Notes

electron/spectron (spectron)

`v19.0.0`

`v18.0.0`

`v17.0.0`

`v16.0.0`

`v15.0.0`

v15.0.0

`v14.0.0`

`v13.0.0`

`v12.0.0`

`v11.1.0`

Upgraded webdriverio to 6.1.20 #631

`v11.0.0`

Updated to Electron v9.0.0

`v10.0.1`

`v10.0.0`

`v9.0.0`

Add support for Electron 7.0.x line

`v8.0.0`

Adds support for Electron's 6.0.x release line.

`v7.0.0`

Adds support for Electron's 5.0.x release line.

`v6.0.0`

Adds support for Electron's 4.0.x release line.

`v5.0.0`

Supports Electron 3.x.y releases.

`v4.0.0`

Supports Electron 2.0.x releases.

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.


          Update dependency spectron to v19

953153e

Author

renovate bot commented Mar 25, 2023

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

Error response from daemon: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit

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

Labels

None yet