Skip to content

Bump rollup from 4.53.3 to 4.59.0 in /packages/workbox-build#3469

Open
dependabot[bot] wants to merge 1 commit intov7from
dependabot/npm_and_yarn/packages/workbox-build/rollup-4.59.0
Open

Bump rollup from 4.53.3 to 4.59.0 in /packages/workbox-build#3469
dependabot[bot] wants to merge 1 commit intov7from
dependabot/npm_and_yarn/packages/workbox-build/rollup-4.59.0

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Feb 28, 2026

Bumps rollup from 4.53.3 to 4.59.0.

Release notes

Sourced from rollup's releases.

v4.59.0

4.59.0

2026-02-22

Features

  • Throw when the generated bundle contains paths that would leave the output directory (#6276)

Pull Requests

v4.58.0

4.58.0

2026-02-20

Features

  • Also support __NO_SIDE_EFFECTS__ annotation before variable declarations declaring function expressions (#6272)

Pull Requests

v4.57.1

4.57.1

2026-01-30

Bug Fixes

  • Fix heap corruption issue in Windows (#6251)
  • Ensure exports of a dynamic import are fully included when called from a try...catch (#6254)

Pull Requests

... (truncated)

Changelog

Sourced from rollup's changelog.

4.59.0

2026-02-22

Features

  • Throw when the generated bundle contains paths that would leave the output directory (#6276)

Pull Requests

4.58.0

2026-02-20

Features

  • Also support __NO_SIDE_EFFECTS__ annotation before variable declarations declaring function expressions (#6272)

Pull Requests

4.57.1

2026-01-30

Bug Fixes

  • Fix heap corruption issue in Windows (#6251)
  • Ensure exports of a dynamic import are fully included when called from a try...catch (#6254)

Pull Requests

... (truncated)

Commits

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 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)
    You can disable automated security fix PRs for this repo from the Security Alerts page.

Bumps [rollup](https://github.com/rollup/rollup) from 4.53.3 to 4.59.0.
- [Release notes](https://github.com/rollup/rollup/releases)
- [Changelog](https://github.com/rollup/rollup/blob/master/CHANGELOG.md)
- [Commits](rollup/rollup@v4.53.3...v4.59.0)

---
updated-dependencies:
- dependency-name: rollup
  dependency-version: 4.59.0
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Feb 28, 2026
@jayaddison
Copy link

The Full_Suite_Mac GitHub Actions test job seems to be failing due to a Chrome version mismatch between the version provided by selenium-assistant compared to the version expected by chromedriver. This is apparent in the build logs at: https://github.com/GoogleChrome/workbox/actions/runs/22528884495/job/65265163096?pr=3469#step:7:1338

The selenium-assistant code seems to install browsers to a .selenium-assistant directory (on non-win32) -- and that's a path that is cached (ref a4d16d9) by the relevant GitHub Actions workflow job here:

- uses: actions/cache@v4
with:
path: ~/.selenium-assistant
key: ${{ runner.os }}

The cache may be expired or out-of-sync with the latest stable release of Chrome-For-Testing (v146 at the time-of-writing).

Since a couple of weeks ago, chromedriver (used by the integration tests here to run Chrome) has expected to use v146: giggio/node-chromedriver#595

(the cache is probably worthwhile in general to reduce the duration and overhead of GitHub Actions CI -- but in this case I think there's a chance that it is the cause of the integration test failure)

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

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant