Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Sep 21, 2021

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@rollup/plugin-node-resolve (source) 13.0.4 -> 13.3.0 age adoption passing confidence

Release Notes

rollup/plugins

v13.3.0

2022-05-02

Features
  • feat: support node: protocol (#​1124)

v13.2.2

2022-05-02

Bugfixes
  • fix: Respect if other plugins resolve the resolution to a different id (#​1181)
  • fix: Revert respect if other plugins resolve the resolution to a different id (ae59ceb)
  • fix: Respect if other plugins resolve the resolution to a different id (f8d4c44)

v13.2.1

2022-04-15

Bugfixes
  • fix: update side effects logic to be deep when glob doesn’t contain / (#​1148)

v13.2.0

2022-04-11

Features
  • feat: Add the ability to pass a function into resolveOnly (#​1152)

v13.1.3

2022-01-05

Bugfixes
  • fix: use correct version when published (#​1063)

v13.1.2

2021-12-31

Bugfixes
  • fix: forward meta-information from other plugins (#​1062)

v13.1.1

2021-12-13

Updates
  • test: add tests for mixing custom exportConditions with browser: true (#​1043)

v13.1.0

2021-12-13

Features
  • feat: expose plugin version (#​1050)

v13.0.6

2021-10-19

Bugfixes

v13.0.5

2021-09-21

Updates
  • docs: fix readme heading depth (#​999)

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 force-pushed the renovate/rollup-plugin-node-resolve-13.x branch from 55c17a6 to 9fe795d Compare October 19, 2021 14:56
@renovate renovate bot changed the title chore(deps): update dependency @rollup/plugin-node-resolve to v13.0.5 chore(deps): update dependency @rollup/plugin-node-resolve to v13.0.6 Oct 19, 2021
@renovate renovate bot force-pushed the renovate/rollup-plugin-node-resolve-13.x branch from 9fe795d to 3f88f47 Compare March 7, 2022 16:00
@renovate renovate bot changed the title chore(deps): update dependency @rollup/plugin-node-resolve to v13.0.6 chore(deps): update dependency @rollup/plugin-node-resolve to v13.1.3 Mar 7, 2022
@renovate renovate bot force-pushed the renovate/rollup-plugin-node-resolve-13.x branch from 3f88f47 to 39d55aa Compare April 25, 2022 01:29
@renovate renovate bot changed the title chore(deps): update dependency @rollup/plugin-node-resolve to v13.1.3 chore(deps): update dependency @rollup/plugin-node-resolve to v13.2.1 Apr 25, 2022
@renovate
Copy link
Contributor Author

renovate bot commented Apr 25, 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: packages/tokens/package-lock.json
npm WARN deprecated read-package-tree@5.3.1: The functionality that this package provided is now in @npmcli/arborist
npm WARN deprecated har-validator@5.1.5: this library is no longer supported
npm WARN deprecated uuid@3.4.0: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
lerna notice cli v4.0.0
lerna notice cli v4.0.0
lerna info Bootstrapping 3 packages
lerna info Installing external dependencies
lerna ERR! npm install --ignore-scripts --ignore-scripts --no-audit --package-lock-only exited 1 in '@multei/storybook'
lerna ERR! npm install --ignore-scripts --ignore-scripts --no-audit --package-lock-only stderr:
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: react-dom@16.14.0
npm ERR! Found: react@17.0.2
npm ERR! node_modules/react
npm ERR!   dev react@"17.0.2" from the root project
npm ERR!   peer react@">=16.3.0" from @emotion/core@10.1.1
npm ERR!   node_modules/@emotion/core
npm ERR!     peer @emotion/core@"^10.0.27" from @emotion/styled@10.0.27
npm ERR!     node_modules/@emotion/styled
npm ERR!       @emotion/styled@"^10.0.27" from @storybook/theming@6.3.8
npm ERR!       node_modules/@storybook/theming
npm ERR!         @storybook/theming@"6.3.8" from @storybook/addon-actions@6.3.8
npm ERR!         node_modules/@storybook/addon-actions
npm ERR!         6 more (@storybook/addons, @storybook/api, ...)
npm ERR!     peer @emotion/core@"^10.0.28" from @emotion/styled-base@10.0.31
npm ERR!     node_modules/@emotion/styled-base
npm ERR!       @emotion/styled-base@"^10.0.27" from @emotion/styled@10.0.27
npm ERR!       node_modules/@emotion/styled
npm ERR!         @emotion/styled@"^10.0.27" from @storybook/theming@6.3.8
npm ERR!         node_modules/@storybook/theming
npm ERR!     3 more (@storybook/theming, @storybook/ui, emotion-theming)
npm ERR!   32 more (@emotion/styled, @emotion/styled-base, ...)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^16.14.0" from react-dom@16.14.0
npm ERR! node_modules/react-dom
npm ERR!   peerOptional react-dom@"^16.8.0 || ^17.0.0" from @storybook/addon-actions@6.3.8
npm ERR!   node_modules/@storybook/addon-actions
npm ERR!     dev @storybook/addon-actions@"6.3.8" from the root project
npm ERR!   peerOptional react-dom@"^16.8.0 || ^17.0.0" from @storybook/addon-links@6.3.8
npm ERR!   node_modules/@storybook/addon-links
npm ERR!     dev @storybook/addon-links@"6.3.8" from the root project
npm ERR!   20 more (@storybook/addons, @storybook/api, @reach/router, ...)
npm ERR! 
npm ERR! Conflicting peer dependency: react@16.14.0
npm ERR! node_modules/react
npm ERR!   peer react@"^16.14.0" from react-dom@16.14.0
npm ERR!   node_modules/react-dom
npm ERR!     peerOptional react-dom@"^16.8.0 || ^17.0.0" from @storybook/addon-actions@6.3.8
npm ERR!     node_modules/@storybook/addon-actions
npm ERR!       dev @storybook/addon-actions@"6.3.8" from the root project
npm ERR!     peerOptional react-dom@"^16.8.0 || ^17.0.0" from @storybook/addon-links@6.3.8
npm ERR!     node_modules/@storybook/addon-links
npm ERR!       dev @storybook/addon-links@"6.3.8" from the root project
npm ERR!     20 more (@storybook/addons, @storybook/api, @reach/router, ...)
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-05-16T00_18_52_615Z-debug-0.log
lerna ERR! npm install --ignore-scripts --ignore-scripts --no-audit --package-lock-only exited 1 in '@multei/storybook'

@renovate renovate bot force-pushed the renovate/rollup-plugin-node-resolve-13.x branch from 39d55aa to 7ac05a3 Compare May 16, 2022 00:19
@renovate renovate bot changed the title chore(deps): update dependency @rollup/plugin-node-resolve to v13.2.1 chore(deps): update dependency @rollup/plugin-node-resolve to v13.3.0 May 16, 2022
@renovate
Copy link
Contributor Author

renovate bot commented Mar 24, 2023

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants