Skip to content
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 jest-puppeteer to v10 #554

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

Update dependency jest-puppeteer to v10 #554

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 11, 2024 •
edited

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
jest-puppeteer (source) 6.2.0 -> 10.0.1 age adoption passing confidence

Release Notes

argos-ci/jest-puppeteer (jest-puppeteer)

v10.0.1

Compare Source

Note: Version bump only for package jest-puppeteer

v10.0.0

Compare Source

Note: Version bump only for package jest-puppeteer

9.0.2 (2023-12-06)

Note: Version bump only for package jest-puppeteer

9.0.1 (2023-10-01)

Bug Fixes

v9.0.2

Compare Source

Note: Version bump only for package jest-puppeteer

v9.0.1

Compare Source

Bug Fixes

v9.0.0

Compare Source

Features
  • drop Node.js v14 support (d7d9833)
BREAKING CHANGES
  • drop Node.js v14 support

8.0.6 (2023-03-24)

Bug Fixes

8.0.5 (2023-03-09)

Note: Version bump only for package jest-puppeteer

8.0.4 (2023-03-08)

Bug Fixes

8.0.3 (2023-03-07)

Bug Fixes

8.0.2 (2023-03-06)

Note: Version bump only for package jest-puppeteer

8.0.1 (2023-03-06)

Note: Version bump only for package jest-puppeteer

v8.0.6

Compare Source

Bug Fixes

v8.0.5

Compare Source

Note: Version bump only for package jest-puppeteer

v8.0.4

Compare Source

Bug Fixes

v8.0.3

Compare Source

Bug Fixes

v8.0.2

Compare Source

Note: Version bump only for package jest-puppeteer

v8.0.1

Compare Source

Note: Version bump only for package jest-puppeteer

v8.0.0

Compare Source

Features
BREAKING CHANGES
    • spawnd now exports { spawd } instead of default to ensure
      compatibilty with ESM
  • toMatch has been renamed toMatchTextContent to avoid collision
    with existing Jest matcher

7.0.1 (2023-02-15)

Note: Version bump only for package jest-puppeteer

v7.0.1

Compare Source

Note: Version bump only for package jest-puppeteer

v7.0.0

Compare Source

Features
BREAKING CHANGES
  • requires puppeteer v19+

Configuration

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

🚦 Automerge: Enabled.

♻ 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 renovate bot enabled auto-merge (rebase) February 11, 2024 02:28
@renovate Renovate
Copy link
Contributor Author

renovate bot commented Feb 11, 2024 •
edited

⚠ 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 unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/puppeteer
npm ERR!   dev puppeteer@"14.1.2" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer puppeteer@">=19" from [email protected]
npm ERR! node_modules/jest-puppeteer
npm ERR!   dev jest-puppeteer@"10.0.1" 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/renovate/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/renovate/cache/others/npm/_logs/2024-05-09T00_02_05_047Z-debug-0.log

@renovate renovate bot force-pushed the renovate/jest-puppeteer-10.x branch 4 times, most recently from ab11cb1 to 83fb847 Compare February 15, 2024 10:57
@renovate renovate bot force-pushed the renovate/jest-puppeteer-10.x branch 2 times, most recently from ec34f4d to d58ca40 Compare February 23, 2024 04:23
@renovate renovate bot force-pushed the renovate/jest-puppeteer-10.x branch 2 times, most recently from 5e3ee45 to 9f24088 Compare March 2, 2024 21:12
@renovate renovate bot force-pushed the renovate/jest-puppeteer-10.x branch from 9f24088 to 0ea8ea2 Compare March 6, 2024 23:01
@renovate renovate bot force-pushed the renovate/jest-puppeteer-10.x branch 6 times, most recently from 8ca5d1d to bef9fb1 Compare March 21, 2024 18:14
@renovate renovate bot force-pushed the renovate/jest-puppeteer-10.x branch 5 times, most recently from dbec4e9 to c0d1290 Compare April 11, 2024 17:59
@renovate renovate bot force-pushed the renovate/jest-puppeteer-10.x branch 2 times, most recently from ea8221b to 555cf7c Compare April 25, 2024 19:03
@renovate renovate bot force-pushed the renovate/jest-puppeteer-10.x branch from 555cf7c to 383ffbb Compare May 9, 2024 00:02
@renovate renovate bot force-pushed the renovate/jest-puppeteer-10.x branch from 383ffbb to be64510 Compare May 24, 2024 22:09
@renovate Renovate
Copy link
Contributor Author

renovate bot commented May 24, 2024 •
edited

⚠️ 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 unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/puppeteer
npm ERR!   dev puppeteer@"14.1.2" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer puppeteer@">=19" from [email protected]
npm ERR! node_modules/jest-puppeteer
npm ERR!   dev jest-puppeteer@"10.0.1" 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/renovate/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/renovate/cache/others/npm/_logs/2024-06-17T12_08_14_247Z-debug-0.log

@renovate renovate bot force-pushed the renovate/jest-puppeteer-10.x branch from be64510 to e743257 Compare May 31, 2024 16:53
@SaintNoodles
Copy link

rip

@renovate renovate bot force-pushed the renovate/jest-puppeteer-10.x branch from e743257 to 2eececd Compare June 10, 2024 03:14
@renovate renovate bot force-pushed the renovate/jest-puppeteer-10.x branch from 2eececd to b0b9a4a Compare June 17, 2024 12:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@renovate-approve renovate-approve[bot] renovate-approve approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
1 participant
@SaintNoodles