Bump rollup from 3.29.4 to 3.29.5

[dependabot]

Bumps rollup from 3.29.4 to 3.29.5.

Changelog

Sourced from rollup's changelog.

rollup changelog

4.22.4

2024-09-21

Bug Fixes

• Fix a vulnerability in generated code that affects IIFE, UMD and CJS bundles when run in a browser context (#5671)

Pull Requests

• #5670: refactor: Use object.prototype to check for reserved properties (@​YuHyeonWook)
• #5671: Fix DOM Clobbering CVE (@​lukastaegert)

4.22.3

2024-09-21

Bug Fixes

• Ensure that mutations in modules without side effects are observed while properly handling transitive dependencies (#5669)

Pull Requests

• #5669: Ensure impure dependencies of pure modules are added (@​lukastaegert)

4.22.2

2024-09-20

Bug Fixes

• Revert fix for side effect free modules until other issues are investigated (#5667)

Pull Requests

• #5667: Partially revert #5658 and re-apply #5644 (@​lukastaegert)

4.22.1

2024-09-20

Bug Fixes

• Revert #5644 "stable chunk hashes" while issues are being investigated

Pull Requests

• #5663: chore(deps): update dependency inquirer to v11 (@​renovate[bot], @​lukastaegert)

... (truncated)

Commits

• dfd233d 3.29.5
• 2ef77c0 Fix DOM Clobbering CVE
• See full diff in compare view

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

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[qodo-code-review]

PR-Agent was enabled for this repository. To continue using it, please link your git user with your CodiumAI identity here.

CI Failure Feedback 🧐

Action: build

Failed stage: Run Tests [❌]

Failure summary: The action failed due to the following reasons: The environment variable ALCHEMY_API_KEY is not set. The error message suggests copying .env.sample to .env and filling in the correct values. The command failed with an exit code 1, indicating an error occurred during the execution of the tests or scripts.

Relevant error logs: 1: ##[group]Operating System 2: Ubuntu ... 464: $ NODE_OPTIONS="--loader ts-node/esm" c8 mocha --require ts-node/register 465: (node:1882) ExperimentalWarning: `--experimental-loader` may be removed in the future; instead use `register()`: 466: --import 'data:text/javascript,import { register } from "node:module"; import { pathToFileURL } from "node:url"; register("ts-node/esm", pathToFileURL("./"));' 467: (Use `node --trace-warnings ...` to show where the warning was created) 468: (node:1894) ExperimentalWarning: `--experimental-loader` may be removed in the future; instead use `register()`: 469: --import 'data:text/javascript,import { register } from "node:module"; import { pathToFileURL } from "node:url"; register("ts-node/esm", pathToFileURL("./"));' 470: (Use `node --trace-warnings ...` to show where the warning was created) 471: Loading dotenv to process .env 472: Error: ALCHEMY_API_KEY environment variable is not set (copy .env.sample to .env and fill in the correct values) ... 501: lib/builder | 4.48 | 0 | 0 | 4.48 | 502: mint-template-builder.ts | 4.48 | 0 | 0 | 4.48 | 11-223 503: lib/simulation | 24.01 | 100 | 0 | 24.01 | 504: simulation.ts | 19.85 | 100 | 0 | 19.85 | ...04,107-115,118-135,138-141 505: tenderly.ts | 33.33 | 100 | 0 | 33.33 | 12-24,28-40,43-49,52-60 506: lib/simulation/types | 100 | 100 | 100 | 100 | 507: tenderly.types.ts | 100 | 100 | 100 | 100 | 508: lib/types | 90.83 | 66.66 | 0 | 90.83 | 509: mint-ingestor-error.ts | 57.69 | 50 | 0 | 57.69 | 16-26 510: mint-template.ts | 100 | 100 | 100 | 100 | 511: ---------------------------|---------|----------|---------|---------|------------------------------- 512: error Command failed with exit code 1. 513: info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. 514: ##[error]Process completed with exit code 1.

---

✨ CI feedback usage guide:

---

The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
The tool analyzes the failed checks and provides several feedbacks:

• Failed stage
• Failed test name
• Failure summary
• Relevant error logs

In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

/checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

Configuration options

• enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
• excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
• enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
• persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
• final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

See more information about the checks tool in the docs.