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 @rollup/plugin-node-resolve to v13.3.0 #6

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

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Aug 1, 2021

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@rollup/plugin-node-resolve (source) 13.0.2 -> 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)

v13.0.4

2021-07-24

Bugfixes
  • fix: Fix bug where JS import was converted to a TS import, resulting in an error when using export maps (#​921)

v13.0.3

2021-07-24

Bugfixes
  • fix: handle browser-mapped paths correctly in nested contexts (#​920)

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 changed the title chore(deps): update dependency @rollup/plugin-node-resolve to v13.0.4 chore(deps): update dependency @rollup/plugin-node-resolve to v13.0.5 Sep 21, 2021
@renovate renovate bot force-pushed the renovate/rollup-plugin-node-resolve-13.x branch from ad224a7 to 2308c38 Compare September 21, 2021 21:48
@renovate renovate bot force-pushed the renovate/rollup-plugin-node-resolve-13.x branch from 2308c38 to 459fc4c Compare March 7, 2022 13:07
@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.1.3 Mar 7, 2022
@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 24, 2022
@renovate renovate bot force-pushed the renovate/rollup-plugin-node-resolve-13.x branch from 459fc4c to f33e18f Compare April 24, 2022 22:55
@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 renovate bot force-pushed the renovate/rollup-plugin-node-resolve-13.x branch from f33e18f to c728385 Compare May 16, 2022 03:32
@renovate
Copy link
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
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant