chore(deps): bump @babel/helpers from 7.25.7 to 7.28.4 in /core/gui

[dependabot]

Bumps @babel/helpers from 7.25.7 to 7.28.4.

Release notes

Sourced from @​babel/helpers's releases.

v7.28.4 (2025-09-05)

Thanks @​gwillen and @​mrginglymus for your first PRs!

🏠 Internal

• babel-core, babel-helper-check-duplicate-nodes, babel-traverse, babel-types
  • #17493 Update Jest to v30.1.1 (@​JLHwung)
• babel-plugin-transform-regenerator
  • #17455 chore: Clean up transform-regenerator (@​liuxingbaoyu)
• babel-core
  • #17474 Switch to @​jridgewell/remapping (@​mrginglymus)

Committers: 5

• Babel Bot (@​babel-bot)
• Bill Collins (@​mrginglymus)
• Glenn Willen (@​gwillen)
• Huáng Jùnliàng (@​JLHwung)
• @​liuxingbaoyu

v7.28.3 (2025-08-14)

👓 Spec Compliance

• babel-helper-create-class-features-plugin, babel-plugin-proposal-decorators, babel-plugin-transform-class-static-block, babel-preset-env
  • #17443 [static blocks] Do not inject new static fields after static code (@​nicolo-ribaudo)

🐛 Bug Fix

• babel-parser
  • #17465 fix(parser/typescript): parse import("./a", {with:{},}) (@​easrng)
  • #17478 fix(parser): stop subscript parsing on async arrow (@​JLHwung)

💅 Polish

• babel-plugin-transform-regenerator, babel-plugin-transform-runtime
  • #17363 Do not save last yield in call in temp var (@​nicolo-ribaudo)

📝 Documentation

• #17448 move eslint-{parser,plugin} docs to the website (@​JLHwung)

🏠 Internal

• #17454 Enable type checking for scripts and babel-worker.cjs (@​JLHwung)

🔬 Output optimization

• babel-plugin-proposal-destructuring-private, babel-plugin-proposal-do-expressions
  • #17444 Optimize do expression output (@​JLHwung)

Committers: 5

• Babel Bot (@​babel-bot)
• Huáng Jùnliàng (@​JLHwung)
• Jam Balaya (@​JamBalaya56562)
• Nicolò Ribaudo (@​nicolo-ribaudo)
• easrng (@​easrng)

... (truncated)

Changelog

Sourced from @​babel/helpers's changelog.

v7.28.4 (2025-09-05)

🏠 Internal

• babel-core, babel-helper-check-duplicate-nodes, babel-traverse, babel-types
  • #17493 Update Jest to v30.1.1 (@​JLHwung)
• babel-plugin-transform-regenerator
  • #17455 chore: Clean up transform-regenerator (@​liuxingbaoyu)
• babel-core
  • #17474 Switch to @​jridgewell/remapping (@​mrginglymus)

v7.28.3 (2025-08-14)

👓 Spec Compliance

• babel-helper-create-class-features-plugin, babel-plugin-proposal-decorators, babel-plugin-transform-class-static-block, babel-preset-env
  • #17443 [static blocks] Do not inject new static fields after static code (@​nicolo-ribaudo)

🐛 Bug Fix

• babel-parser
  • #17465 fix(parser/typescript): parse import("./a", {with:{},}) (@​easrng)
  • #17478 fix(parser): stop subscript parsing on async arrow (@​JLHwung)

💅 Polish

• babel-plugin-transform-regenerator, babel-plugin-transform-runtime
  • #17363 Do not save last yield in call in temp var (@​nicolo-ribaudo)

📝 Documentation

• #17448 move eslint-{parser,plugin} docs to the website (@​JLHwung)

🏠 Internal

• #17454 Enable type checking for scripts and babel-worker.cjs (@​JLHwung)

🔬 Output optimization

• babel-plugin-proposal-destructuring-private, babel-plugin-proposal-do-expressions
  • #17444 Optimize do expression output (@​JLHwung)

v7.28.2 (2025-07-24)

🐛 Bug Fix

• babel-types
  • #17445 [babel 7] Make operator param in t.tsTypeOperator optional (@​nicolo-ribaudo)
• babel-helpers, babel-plugin-transform-async-generator-functions, babel-plugin-transform-regenerator, babel-preset-env, babel-runtime-corejs3
  • #17441 fix: regeneratorDefine compatibility with es5 strict mode (@​liuxingbaoyu)

v7.28.1 (2025-07-12)

🐛 Bug Fix

• babel-plugin-transform-async-generator-functions, babel-plugin-transform-regenerator
  • #17426 fix: regenerator correctly handles throw outside of try (@​liuxingbaoyu)

📝 Documentation

• babel-types
  • #17422 Add missing FunctionParameter docs (@​JLHwung)

... (truncated)

Commits

• 35055e3 v7.28.4
• 18d88b8 Improve @​babel/core typings (#17471)
• ef155f5 v7.28.3
• 741cbd2 chore: fix various typos across codebase (#17476)
• cac0ff4 v7.28.2
• f743094 fix: regeneratorDefine compatibility with es5 strict mode (#17441)
• baa4cb8 v7.27.6
• fdbf1b3 fix: finally causes unexpected return value (#17366)
• 7d06930 v7.27.4
• 5b9468d Reduce regenerator size more (#17287)
• Additional commits viewable in compare view

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

[aglinxinyuan]

@kunwp1, please review the PR.

[kunwp1]

For this library, our frontend code doesn’t use it directly. Instead, Angular and Nx rely on it indirectly to ensure TypeScript compiles into browser-compatible code. In this case, is there a protocol or systematic way to check for regressions? Do you think running CI tests (frontend unit tests) is sufficient?

➜  gui git:(main) yarn why @babel/helpers
├─ @babel/core@npm:7.22.9
│  └─ @babel/helpers@npm:7.28.4 (via npm:^7.22.6)
│
├─ @babel/core@npm:7.23.2
│  └─ @babel/helpers@npm:7.28.4 (via npm:^7.23.2)
│
└─ @babel/core@npm:7.25.8
   └─ @babel/helpers@npm:7.28.4 (via npm:^7.25.7)
➜  gui git:(main) yarn why @babel/core
├─ @angular-devkit/build-angular@npm:16.2.12
│  └─ @babel/core@npm:7.22.9 (via npm:7.22.9)
│
├─ @angular-devkit/build-angular@npm:16.2.16
│  └─ @babel/core@npm:7.22.9 (via npm:7.22.9)
│
├─ @angular-devkit/build-angular@npm:16.2.12 [125e9]
│  └─ @babel/core@npm:7.22.9 (via npm:7.22.9)
│
├─ @angular-devkit/build-angular@npm:16.2.16 [e8b71]
│  └─ @babel/core@npm:7.22.9 (via npm:7.22.9)
│
├─ @angular/compiler-cli@npm:16.2.12
│  └─ @babel/core@npm:7.23.2 (via npm:7.23.2)
│
├─ @angular/compiler-cli@npm:16.2.12 [125e9]
│  └─ @babel/core@npm:7.23.2 (via npm:7.23.2)
│
├─ @angular/localize@npm:16.2.12
│  └─ @babel/core@npm:7.23.2 (via npm:7.23.2)
│
├─ @angular/localize@npm:16.2.12 [125e9]
│  └─ @babel/core@npm:7.23.2 (via npm:7.23.2)
│
├─ @nx/js@npm:20.0.3
│  └─ @babel/core@npm:7.25.8 (via npm:^7.23.2)
│
├─ @nx/js@npm:20.0.3 [51472]
│  └─ @babel/core@npm:7.25.8 (via npm:^7.23.2)
│
├─ @nx/webpack@npm:20.0.3
│  └─ @babel/core@npm:7.25.8 (via npm:^7.23.2)
│
└─ istanbul-lib-instrument@npm:5.2.1
   └─ @babel/core@npm:7.25.8 (via npm:^7.12.3)

[aglinxinyuan]

Running the unit tests locally, building and running Texera on your machine, and testing a few key functionalities in the Hub and Workflow Editor should be sufficient.

[kunwp1]

I think we should have clear guidelines on which key features of Texera need to be tested manually. Since Texera has a lot of features, I don’t want to risk overlooking something important during this review process and encountering issues later.

[aglinxinyuan]

I think we should have clear guidelines on which key features of Texera need to be tested manually. Since Texera has a lot of features, I don’t want to risk overlooking something important during this review process and encountering issues later.

We can decide that later. For this PR, since the library is frontend-only, you only need to verify the key frontend features. Please test the following:
• Add a workflow
• Delete a workflow
• Add a dataset
• Upload a file to a dataset
• Drag an operator into the workflow editor
• Run the workflow and view the results
• Delete the operator
Based on my knowledge, this list should be more than enough for this PR.

[kunwp1]

Thanks! I'll review the PR based on the list

[kunwp1]

LGTM! Tested all the key features.