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.

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

chore(deps): update dependency @vue/test-utils to v2 #97

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 12, 2022

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@vue/test-utils ^1.1.3 -> ^2.0.0 age adoption passing confidence

Release Notes

vuejs/test-utils (@​vue/test-utils)

v2.4.5

Compare Source

What's Changed

New Contributors

Full Changelog: vuejs/test-utils@v2.4.4...v2.4.5

v2.4.4

Compare Source

What's Changed

New Contributors

Full Changelog: vuejs/test-utils@v2.4.3...v2.4.4

v2.4.3

Compare Source

What's Changed

Full Changelog: vuejs/test-utils@v2.4.2...v2.4.3

v2.4.2

Compare Source

What's Changed

Fix
Docs
Chore

New Contributors

Full Changelog: vuejs/test-utils@v2.4.1...v2.4.2

v2.4.1

Compare Source

What's Changed

Fixes
Docs
(Dev) Dependencies

New Contributors

Full Changelog: vuejs/test-utils@v2.4.0...v2.4.1

v2.4.0

Compare Source

Note: there might be some minor breaking changes around types. We tried hard to avoid this and tested a few different projects, but there was some major under the hood changes relating to types (which should improve the TypeScript experience). See the note at the top of the previous release, 2.4.0-alpha.2: https://github.com/vuejs/test-utils/releases/tag/v2.4.0-alpha.2

Between the last main release, v2.3.2, and v2.4.0, there were three alphas:

Please see those release notes for changes if you are updating from v2.3.2. Again, there should not be any major changes, and you code and tests should continue to work as before without any changes.

If you do encounter breaking changes transitioning from 2.3.x -> 2.4.x, please file an issue.

v2.3.2

Compare Source

What's Changed

New Contributors

Full Changelog: vuejs/test-utils@v2.3.1...v2.3.2

v2.3.1

Compare Source

What's Changed

New Contributors

Full Changelog: vuejs/test-utils@v2.3.0...v2.3.1

v2.3.0

Compare Source

What's Changed

renderToString is merged for SSR testing, thanks to @​wobsoriano and @​cexbrayat!

New Contributors

Full Changelog: vuejs/test-utils@2.2.10...v2.3.0

v2.2.10

Compare Source

What's Changed

Full Changelog: vuejs/test-utils@v2.2.9...2.2.10

v2.2.9

Compare Source

What's Changed

Full Changelog: vuejs/test-utils@v2.2.8...v2.2.9

v2.2.8

Compare Source

What's Changed

Full Changelog: vuejs/test-utils@v2.2.7...v2.2.8

v2.2.7

Compare Source

Fixes

Docs

Chore

New Contributors

Full Changelog: vuejs/test-utils@v2.2.6...v2.2.7

v2.2.6

Compare Source

What's Changed

Full Changelog: vuejs/test-utils@v2.2.5...v2.2.6

v2.2.5

Compare Source

What's Changed

New Contributors

Full Changelog: vuejs/test-utils@v2.2.4...v2.2.5

v2.2.4

Compare Source

What's Changed

Full Changelog: vuejs/test-utils@v2.2.3...v2.2.4

v2.2.3

Compare Source

What's Changed

Full Changelog: vuejs/test-utils@v2.2.2...v2.2.3

v2.2.2

Compare Source

Fixes

Other

Full Changelog: vuejs/test-utils@v2.2.1...v2.2.2

v2.2.1

Compare Source

What's Changed

Full Changelog: vuejs/test-utils@v2.2.0...v2.2.1

v2.2.0

Compare Source

What's Changed

Features
Fixes
Other

New Contributors

Full Changelog: vuejs/test-utils@v2.1.0...v2.2.0

v2.1.0

Compare Source

What's Changed

Fixes

Other

Chore

New Contributors

Full Changelog: vuejs/test-utils@v2.0.2...v2.1.0

v2.0.2

Compare Source

What's Changed

Fixes
Docs
Chore/Other

New Contributors

Full Changelog: vuejs/test-utils@v2.0.1...v2.0.2

v2.0.1

Compare Source

Test Utils is quite stable now, so most of the changes here are minor fixes.

The next "big ticket" feature will be SSR support. You can track it here: https://github.com/vuejs/test-utils/pull/1572

Fixes

Chores/Dependencies


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
Contributor Author

renovate bot commented Jul 12, 2022

⚠ 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: spolyr@undefined
npm ERR! Found: vue@2.7.4
npm ERR! node_modules/vue
npm ERR!   vue@"^2.6.14" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer vue@"^3.0.1" from @vue/test-utils@2.0.2
npm ERR! node_modules/@vue/test-utils
npm ERR!   dev @vue/test-utils@"^2.0.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/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/2022-07-12T11_16_49_759Z-debug-0.log

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.

None yet

0 participants