build: Bump brace-expansion, ui5-tooling-modules and ui5-tooling-stringreplace in /internal/e2e-tests/fixtures/application.a

[dependabot]

Bumps brace-expansion to 2.1.2 and updates ancestor dependencies brace-expansion, ui5-tooling-modules and ui5-tooling-stringreplace. These dependencies need to be updated together.

Updates brace-expansion from 2.1.0 to 2.1.2

Release notes

Sourced from brace-expansion's releases.

v2.1.1

• Backport v5.0.6 change to v2 (#109) c3a817c

---

juliangruber/brace-expansion@v2.1.0...v2.1.1

Commits

• 9e67a3b 2.1.2
• 835d6be fix: v2 backport for CVE-2026-13149 (#123)
• 64b71d3 2.1.1
• c3a817c Backport v5.0.6 change to v2 (#109)
• See full diff in compare view

Updates ui5-tooling-modules from 3.35.0 to 3.37.8

Changelog

Sourced from ui5-tooling-modules's changelog.

3.37.8

Patch Changes

• #1412 6d989b3 Thanks @​petermuessig! - Fix recognition of native (non-UI5) Web Components whose components extend HTMLElement directly instead of UI5Element (regression since 3.36.0, #1410).
  • Guard the superclass lookup in WebComponentRegistry#connectSuperclass against an undefined superclassLookupName (?.startsWith), which previously crashed with Cannot read properties of undefined (reading 'startsWith') for web components without a resolvable superclass.
  • In rollup-plugin-webcomponents, treat a custom element without a UI5 superclass as a native Web Component: load only the component module itself instead of prepending an import of the package or of @ui5/webcomponents-base (which such components neither need nor understand — no scoping or package runtime is required). The generated UI5 control wrapper imports the WebComponent base class accordingly and skips the JSDoc superclass serialization when the superclass metadata is missing.
  • Add a webc-package showcase (a plain HTMLElement-based CustomAlertButton with a Custom Elements Manifest) plus a regression test and snapshot, and consume it from the ui5-tsapp showcase.

3.37.7

Patch Changes

• #1406 535ec0f Thanks @​petermuessig! - Sync defaultValue serialization between rollup-plugin-webcomponents and the Handlebars json helper so the generated UI5 metadata is identical regardless of code path.
  • In rollup-plugin-webcomponents, pass a replacer to JSON.stringify that mirrors the Handlebars helper: drop undefined/"undefined" defaults, keep "" as-is, and JSON.parse everything else so booleans, numbers, objects, and quoted strings come out as proper JSON values (e.g. true instead of "true", "Button" instead of '"Button"').
  • Drop non-parseable values with a warning instead of emitting invalid JSON.
  • Added cross-reference comments on both sides to keep the two implementations in sync.

3.37.6

Patch Changes

• #1404 f3244a2 Thanks @​petermuessig! - Fix JSDoc generation for enum types and defaultValue handling in the generated UI5 metadata.
  • Use the derived UI5 class name (instead of the raw enum name) in the @ui5-module-override directive emitted by JSDocSerializer, so the override matches the generated module.
  • Emit moduleType: module:<slashed-qualified-name> for enum-typed properties so the downstream JSDoc build/validation can resolve enum references.
  • Track _ui5QualifiedNameSlashes and _derivedUi5ClassName on enum definitions when ingesting the custom-elements metadata.
  • Drop the ad-hoc defaultValue cast and the string-escape stripping; pass the raw propDef.default through so numeric, boolean, and object defaults survive code generation.
  • Special-case defaultValue in the Handlebars json helper to inject literal values without quoting, and to omit the property when the default is "undefined".

3.37.5

Patch Changes

• #1401 55f9a53 Thanks @​petermuessig! - Restore emission of the replacement module for "module"-typed entry chunks in rollup-plugin-webcomponents.js. c61afbd6 introduced a re-export stub at the original module id so that consumers importing a Web Component module directly (rather than via its package) still resolve through the generated UI5 wrapper. #1310 later added the "module" type to resolveId/load to prepend the @ui5/webcomponents-base import for such entries, but in doing so changed the generateBundle guard from if (type) to if (type && type !== "module") — silently dropping the replacement stub and breaking direct imports of Web Component modules again. The guard is restored and the "module" branch now emits the same sap.ui.define([...]) re-export the other types do.

3.37.4

Patch Changes

• #1400 848bc70 Thanks @​petermuessig! - Detect custom Web Components via a new WebComponentRegistryHelper.isCustomElement(classDef) predicate that walks the full superclass chain (skipping the UI5Element base class itself, which is paradoxically flagged as a custom element in the metadata). Replaces an inlined check in rollup-plugin-webcomponents.js whose hand-rolled superclass walk only looked at the direct superclass and could loop on a const-bound class reference. When a class is recognized as a custom element only via inheritance, a warning is now logged so the upstream custom-elements.json can be fixed to flag the subclass directly.

• #1398 b4153fa Thanks @​petermuessig! - Guard the complex-type lookup in WebComponentRegistry#parseComplexType against type references that have no module. WebComponentRegistryHelper.deriveCacheKey returns undefined for such references, which previously caused the cross-package lookup and "global import" fallback to misfire (e.g. logging Reference package '…' for complex type '…' not found and producing unusable cache entries). When typeInfoRef.module is missing, skip the complex-type resolution entirely and fall through to the any fallback.

3.37.3

Patch Changes

• #1386 f96206f Thanks @​petermuessig! - fix(ui5-tooling-modules): keep Node.js 20 support by holding ignore-walk at ^8.0.0

  ignore-walk@9 is a Node-engines-only bump (no API changes) that raises the required Node.js version to ^22.22.2 || ^24.15.0 || >=26.0.0. Since the only usage site is unchanged between v8 and v9, downgrade to ^8.0.0 so the package keeps working on Node.js 20 (^20.17.0 || >=22.9.0). See DEPENDENCIES.md for the rationale and the conditions under which this hold-back can be lifted.

... (truncated)

Commits

• 80e2fbe chore(release): publish
• 6d989b3 fix(ui5-tooling-modules): support native (non-UI5) Web Components (#1410)
• feed1f2 chore(release): publish
• 5d41944 fix(ui5-tooling-modules): sync defaultValue handling between rollup plugin an...
• e65335d chore(release): publish
• f3244a2 test(ui5-tooling-modules): update fixtures and snapshots for JSDoc enum + def...
• 9c4a325 fix(ui5-tooling-modules): correct JSDoc generation for enums and defaultValue...
• 80b9ec8 chore(release): publish
• 0830a65 test(ui5-tooling-modules): update @​luigi-project/container snapshot for resto...
• 55f9a53 fix(ui5-tooling-modules): restore replacement chunk for direct webc module im...
• Additional commits viewable in compare view

Updates ui5-tooling-stringreplace from 3.6.0 to 3.6.2

Changelog

Sourced from ui5-tooling-stringreplace's changelog.

3.6.2

Patch Changes

• #1370 dd71c42 Thanks @​petermuessig! - Bump minimatch from v7 to v10. v9 dropped the default export, so the five require("minimatch") sites were switched to the named export const { minimatch } = require("minimatch"). The runtime call shape minimatch(path, pattern) is unchanged. minimatch 8 raised the Node floor to 20+, which already matches the workspace engines (Node 22 in CI).

All notable changes to this project will be documented in this file. See Conventional Commits for commit guidelines.

3.6.1 (2026-05-21)

Note: Version bump only for package ui5-tooling-stringreplace

Commits

• 5708388 chore(release): publish
• 326d02a chore: bump minimatch from 7 to 10 across packages
• 0e1de5b chore(release): publish
• 804db50 chore: simplify LICENSE and standardize README license sections (#1350)
• 153841c chore: update dependencies and bump OpenUI5 to 1.148.0 (#1349)
• See full diff in compare view

[d3xter666]

@dependabot recreate