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

fix(deps): update dependency vanilla-framework to v3.15.1 - autoclosed #9

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 6, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
vanilla-framework (source) 3.14.0 -> 3.15.1 age adoption passing confidence

Release Notes

canonical/vanilla-framework (vanilla-framework)

v3.15.1

Compare Source

👋 The last release of Vanilla v3

With focus on new major release of Vanilla 4.0 this 3.15.1 is likely the last release of Vanilla v3 line. We may release some hot-fixes if any serious bugs are found, but no new features or maintenance updates are planned for v3 anymore.

Getting Vanilla Framework

Install with NPM: https://www.npmjs.com/package/vanilla-framework
Visit the documentation at https://vanillaframework.io/docs

New in Vanilla v3.15.1

🐛 Bug Fixes
🔨 Maintenance

New Contributors

Full Changelog: canonical/vanilla-framework@v3.15.0...v3.15.1

v3.15.0

Compare Source

Getting Vanilla Framework

Install with NPM: https://www.npmjs.com/package/vanilla-framework
Visit the documentation at https://vanillaframework.io/docs

New in Vanilla v3.15.0

🚀 Features

📝 Documentation

🔨 Maintenance

Full Changelog: canonical/vanilla-framework@v3.14.0...v3.15.0


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 renovate bot requested a review from a team as a code owner July 6, 2023 02:56
@renovate
Copy link
Contributor Author

renovate bot commented Jul 6, 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: ui/package-lock.json
/usr/local/bin/docker: line 4: .: filename argument required
.: usage: . filename [arguments]
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @canonical/react-components@0.42.0
npm ERR! Found: vanilla-framework@3.15.1
npm ERR! node_modules/vanilla-framework
npm ERR!   vanilla-framework@"3.15.1" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer vanilla-framework@"3.14.0" from @canonical/react-components@0.42.0
npm ERR! node_modules/@canonical/react-components
npm ERR!   @canonical/react-components@"0.42.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: vanilla-framework@3.14.0
npm ERR! node_modules/vanilla-framework
npm ERR!   peer vanilla-framework@"3.14.0" from @canonical/react-components@0.42.0
npm ERR!   node_modules/@canonical/react-components
npm ERR!     @canonical/react-components@"0.42.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! 
npm ERR! For a full report see:
npm ERR! /tmp/worker/c321de/0560d9/cache/others/npm/_logs/2023-08-15T05_51_37_297Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/worker/c321de/0560d9/cache/others/npm/_logs/2023-08-15T05_51_37_297Z-debug-0.log

@codecov
Copy link

codecov bot commented Jul 6, 2023

Codecov Report

Merging #9 (e39e115) into main (5b40b79) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main       #9   +/-   ##
=======================================
  Coverage   72.77%   72.77%           
=======================================
  Files          11       11           
  Lines        1304     1304           
=======================================
  Hits          949      949           
  Misses        290      290           
  Partials       65       65           

@renovate renovate bot force-pushed the renovate/vanilla-framework-3.x branch 2 times, most recently from dd8a273 to b82a82a Compare July 10, 2023 07:06
@renovate renovate bot force-pushed the renovate/vanilla-framework-3.x branch from b82a82a to 7d09acd Compare July 19, 2023 16:02
@renovate renovate bot force-pushed the renovate/vanilla-framework-3.x branch 2 times, most recently from e7c4e09 to fcae0da Compare July 27, 2023 15:37
@renovate renovate bot force-pushed the renovate/vanilla-framework-3.x branch from fcae0da to 3038f82 Compare August 10, 2023 08:09
@renovate renovate bot force-pushed the renovate/vanilla-framework-3.x branch from 3038f82 to e39e115 Compare August 15, 2023 05:51
@renovate renovate bot changed the title fix(deps): update dependency vanilla-framework to v3.15.1 fix(deps): update dependency vanilla-framework to v3.15.1 - autoclosed Aug 23, 2023
@renovate renovate bot closed this Aug 23, 2023
@renovate renovate bot deleted the renovate/vanilla-framework-3.x branch August 23, 2023 08:19
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