taro icon indicating copy to clipboard operation
taro copied to clipboard

Published 20 hours ago • verified publisher icon NervJS

chore(deps-dev): bump rollup from 3.21.5 to 4.14.2

Open dependabot[bot] opened this issue 1 year ago • 2 comments

Bumps rollup from 3.21.5 to 4.14.2.

Release notes

Sourced from rollup's releases.

v4.14.2

4.14.2

2024-04-12

Bug Fixes

  • Do not create invalid code when reexporting both a namespace and the default export from that namespace (#5466)
  • Ensure ppc64 platform is properly detected (#5460)

Pull Requests

v4.14.1

4.14.1

2024-04-07

Bug Fixes

  • Show better error when running on musl Linux where the musl build is not supported (#5454)

Pull Requests

v4.14.0

4.14.0

2024-04-03

Features

  • Display error causes in Rollup CLI (#5422)
  • Add basic support for explicit resource management via "using" and "await using" (#5423)

Pull Requests

... (truncated)

Changelog

Sourced from rollup's changelog.

4.14.2

2024-04-12

Bug Fixes

  • Do not create invalid code when reexporting both a namespace and the default export from that namespace (#5466)
  • Ensure ppc64 platform is properly detected (#5460)

Pull Requests

4.14.1

2024-04-07

Bug Fixes

  • Show better error when running on musl Linux where the musl build is not supported (#5454)

Pull Requests

4.14.0

2024-04-03

Features

  • Display error causes in Rollup CLI (#5422)
  • Add basic support for explicit resource management via "using" and "await using" (#5423)

Pull Requests

... (truncated)

Commits
  • 7275328 4.14.2
  • cfbaaaa Ensure reexported namespaces do not prevent creation of default export helper...
  • 2fdfe1c chore(deps): update dependency eslint-plugin-unicorn to v52 (#5468)
  • 4e72323 chore(deps): lock file maintenance (#5470)
  • e2a0539 chore(deps): lock file maintenance minor/patch updates (#5469)
  • eebf061 Add high-level architecture documentation (#5456)
  • 8c31e9b chore: tweak the comment about files should not be edited (#5463)
  • b957e1d Fix ppc64le target (#5460)
  • 0b665c3 4.14.1
  • 555982a Improve error message when running on unsupported MUSL Linux (#5454)
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

dependabot[bot] avatar Apr 12 '24 15:04 dependabot[bot]

欢迎提交 PR~ Taro 非常感谢您对开源事业做出的贡献！🌷🌷🌷

一般 PR 会在一到两周内进行 review，成功合入后会随下一个版本进行发布。

Review 需要耗费大量时间，所以请遵循以下规范，协助我们提高 review 效率🙏🙏🙏

  1. 详细介绍 PR 的背景（非常重要，例如解决了什么问题，该问题如何复现等）
  2. 确保 CI 顺利运行。
  3. 最好能提供对应的测试用例。

为了更好地进行沟通，请加入 Taro 开发者微信群：

taro-bot2[bot] avatar Apr 12 '24 15:04 taro-bot2[bot]

欢迎提交 PR~ Taro 非常感谢您对开源事业做出的贡献！🌷🌷🌷

一般 PR 会在一到两周内进行 review，成功合入后会随下一个版本进行发布。

Review 需要耗费大量时间，所以请遵循以下规范，协助我们提高 review 效率🙏🙏🙏

  1. 详细介绍 PR 的背景（非常重要，例如解决了什么问题，该问题如何复现等）
  2. 确保 CI 顺利运行。
  3. 最好能提供对应的测试用例。

为了更好地进行沟通，请加入 Taro 开发者微信群：

taro-bot2[bot] avatar Apr 12 '24 15:04 taro-bot2[bot]

Superseded by #15612.

dependabot[bot] avatar May 03 '24 07:05 dependabot[bot]