Skip to content
This repository has been archived by the owner on Feb 22, 2024. It is now read-only.

Update dependency geckodriver to v4 #69

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented May 29, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
geckodriver ^2.0.4 -> ^4.0.0 age adoption passing confidence

Release Notes

webdriverio-community/node-geckodriver (geckodriver)

v4.2.1: Release 4.2.1

Compare Source

v4.2.0: Release 4.2.0

Compare Source

v4.1.3: Release 4.1.3

Compare Source

  • don't propagate cacheDir to driver (e4ad2a9)

v4.1.2: Release 4.1.2

Compare Source

v4.1.1: Release 4.1.1

Compare Source

v4.1.0: Release 4.1.0

Compare Source

v4.0.5: Release 4.0.5

Compare Source

v4.0.4: Release 4.0.4

Compare Source

v4.0.3: Release 4.0.3

Compare Source

v4.0.2: Release 4.0.2

Compare Source

v4.0.1

Compare Source

Changelog:

v4.0.0: Release 4.0.0

Compare Source

💥 Breaking Change
  • deprecate Node.js v14 and require v16.13 as minimum version
  • removed version export (please raise an issue if you care about this feature)
  • removed path export (use new download export to get the path to Geckodriver)
  • removed stop export (use p.kill() instead)
  • arguments for export start method changed from string[] to typed object
🚀 New Feature
  • auto-detect latest Geckodriver version
💅 Polish
  • improve and update documentation
🏠 Internal
  • switch to TypeScript
  • switch to ESM with CJS export
  • update Node.js versions for development to v20
📝 Documentation
  • set up tests and CI pipelines
  • set up continues deployment workflows aligned with other WebdriverIO projects

v3.2.0

Compare Source

v3.1.0

Compare Source

v3.0.2

Compare Source

v3.0.1

Compare Source

v3.0.0

Compare Source


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 has been generated by Mend Renovate. View repository job log here.

@renovate
Copy link
Author

renovate bot commented May 29, 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
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @vue/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/eslint
npm ERR!   dev eslint@"^8.1.0" from the root project
npm ERR!   peer eslint@"^6.0.0 || ^7.0.0 || ^8.0.0" from @typescript-eslint/[email protected]
npm ERR!   node_modules/@typescript-eslint/eslint-plugin
npm ERR!     dev @typescript-eslint/eslint-plugin@"^5.2.0" from the root project
npm ERR!     peer @typescript-eslint/eslint-plugin@"^5.0.0" from @vue/[email protected]
npm ERR!     node_modules/@vue/eslint-config-typescript
npm ERR!       dev @vue/eslint-config-typescript@"^9.0.0" from the root project
npm ERR!   14 more (@typescript-eslint/experimental-utils, eslint-utils, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer eslint@"^7.12.1" from @vue/[email protected]
npm ERR! node_modules/@vue/eslint-config-standard
npm ERR!   dev @vue/eslint-config-standard@"^6.1.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/eslint
npm ERR!   peer eslint@"^7.12.1" from @vue/[email protected]
npm ERR!   node_modules/@vue/eslint-config-standard
npm ERR!     dev @vue/eslint-config-standard@"^6.1.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/worker/2216eb/0296fb/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/worker/2216eb/0296fb/cache/others/npm/_logs/2023-05-29T23_55_28_684Z-debug-0.log

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants