Skip to content

Update dependency @rollup/plugin-node-resolve to v13.3.0 #79

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

Merged
merged 1 commit into from
May 13, 2022

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 2, 2022

WhiteSource Renovate

This PR contains the following updates:

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

Configuration

📅 Schedule: 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, click this checkbox.

This PR has been generated by WhiteSource Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/rollup-plugin-node-resolve-13.x branch from 8504cd0 to 059d96f Compare May 13, 2022 11:02
@atherdon atherdon merged commit bff2f0a into main May 13, 2022
@renovate renovate bot deleted the renovate/rollup-plugin-node-resolve-13.x branch May 13, 2022 16:56
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.

2 participants