11362 Commits (fe5e82a2e1bafc6ca7ce5ff53ff4dec3dc795550)

 

All Branches   

Search

Author	SHA1	Message	Date
Rich Harris	fe5e82a2e1	Merge branch 'main' into svelte-custom-renderer-unified-mount-api	2 months ago
Rich Harris	5300843e86	chore: bump playwright (#18319) ... hopefully this will fix the CI timeouts	2 months ago
Rich Harris	3ac0f53dea	fix	2 months ago
Simon H	59d3a36f82	feat: allow declarations in the template (#18282) ... Allows `{let/const ...}` declarations in all places (and more) where we already allow `{@const ...}` (which will eventually get deprecated in favor of this new feature). Closes: #16490 Companion PRs: - https://github.com/sveltejs/language-tools/pull/3033 - https://github.com/sveltejs/prettier-plugin-svelte/pull/533 - https://github.com/sveltejs/eslint-plugin-svelte/pull/1533 - https://github.com/sveltejs/svelte-eslint-parser/pull/891 --------- Co-authored-by: Rich Harris <rich.harris@vercel.com>	2 months ago
Rich Harris	656dae6780	chore: try and discourage slop, even a tiny bit (#18293) ... i don't know how to stem the flood of slop PRs but maybe this will help a tiny bit --------- Co-authored-by: vercel[bot] <35613825+vercel[bot]@users.noreply.github.com>	2 months ago
Rich Harris	3fad9cf838	chore: fix browser-support regression check (#18316) ... vercel bot caught this in the release PR https://github.com/sveltejs/svelte/pull/18315#pullrequestreview-4383622174	2 months ago
Rich Harris	a9e82dd388	chore: remove `on_fork_commit` (#18318) ... Simon thinks it was because he thought that committing the fork != committing the batch, and that this could result in an error boundary showing up too late. But that's not the case	2 months ago
Rich Harris	efb23b221e	preserve treeshakeability	2 months ago
Rich Harris	bff25dd718	tweak	2 months ago
Rich Harris	55807fcdbc	Merge branch 'svelte-custom-renderer' into svelte-custom-renderer-unified-mount-api	2 months ago
Rich Harris	41764ad8eb	merge main	2 months ago
Rich Harris	2be39505c0	fix	2 months ago
Rich Harris	48665293bd	use `mount(...)` with `renderer` instead of introducing a new API	2 months ago
Mathias Picker	a9916053d9	perf: use createElement instead of createElementNS for HTML elements (#18262) ... ## Summary The current wrapper always calls `document.createElementNS(namespace ?? NAMESPACE_HTML, tag, options)` — even for HTML elements (the >99% case), and even when `options` would be `undefined`. Two effects compound: 1. **Route HTML elements through `createElement`** — Blink has a fast path that skips the namespace lookup `createElementNS` always performs. 2. **Omit the trailing `undefined` argument** — V8/Blink take a slower path for `createElementNS(ns, tag, undefined)` (and `createElement(tag, undefined)`) than for the bare 2-arg form. This applies symmetrically to the SVG/MathML branch, where the wrapper now also avoids the `undefined` 3rd arg. The wrapper dispatches to the fastest call shape for every input — `{HTML, non-HTML}` × `{with is, without is}` × no `undefined` ever. ## Affects Every place Svelte constructs a DOM element internally: `<svelte:element>`, `run_scripts`, the per-component `<style>` injector, the `{@html}` wrapper, and the `<template>` element used to clone string templates. ## Numbers Measured in headless Chromium (Chromium 145) using the browser bench harness from #18261, 2–3 runs, median. Lower per-call is better; higher hz is better. ### Raw call shapes (what each shape costs in the browser) | | hz | per-call | | ------------------------------------------- | -------: | -------: | | `createElement(tag)` | ~1,210k | ~0.83 µs | | `createElement(tag, undefined)` | ~901k | ~1.11 µs | | `createElementNS(NS_HTML, tag)` | ~913k | ~1.10 µs | | `createElementNS(NS_HTML, tag, undefined)` | ~630k | ~1.59 µs | | `createElement(tag, { is })` | ~484k | ~2.07 µs | | `createElementNS(SVG_NS, tag)` | ~333k | ~3.01 µs | | `createElementNS(SVG_NS, tag, undefined)` | ~303k | ~3.30 µs | | `createElementNS(SVG_NS, tag, { is })` | ~245k | ~4.08 µs | Two stable effects fall out: - **Trailing `undefined` is consistently slower** than the bare form — ~26% on `createElement`, ~31% on `createElementNS` (HTML), ~10% on `createElementNS` (SVG). - **`createElement` skips a namespace lookup** that `createElementNS` always performs — ~32% delta for equal-shape calls (`createElement(tag)` vs `createElementNS(NS_HTML, tag)`). ### Per-case impact of this PR | Case (namespace, `is`) | Old wrapper call | Old hz | New wrapper call | New hz | Speedup | | ----------------------------- | --------------------------------------------- | --------: | ------------------------------ | --------: | ------: | | HTML, no `is` (dominant path) | `createElementNS(NS_HTML, tag, undefined)` | ~630k | `createElement(tag)` | ~1,210k | **~92%** (1.92×) | | HTML, with `is` | `createElementNS(NS_HTML, tag, { is })` | (slow) | `createElement(tag, { is })` | ~484k | similar to above (just the NS-skip) | | SVG/MathML, no `is` | `createElementNS(ns, tag, undefined)` | ~303k | `createElementNS(ns, tag)` | ~333k | **~10%** | | SVG/MathML, with `is` | `createElementNS(ns, tag, { is })` | ~245k | same | ~245k | no change | No measurable change in JSDOM (both shapes route through the same JS implementation there). The headline gain — **~92% on the dominant HTML-no-`is` path** — combines both effects roughly equally: dropping the `undefined` (~46%) and switching to `createElement` (~32%). Wrapper-vs-raw was also verified: the new wrapper measured to within ±2% of raw `document.createElement(tag)` for the HTML-no-`is` case, so the function-call indirection adds no measurable overhead. See #18261 for the benchmark and methodology. ## Test plan - [x] All 5881 runtime tests still pass (runtime-runes + runtime-legacy) - [x] `<svelte:element xmlns={null}>` correctly falls back to HTML (covered by existing `dynamic-element-dynamic-namespace` test) - [x] SVG/MathML namespaces still go through `createElementNS` - [x] Custom-element `is` option still honoured on both branches 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2 months ago
Mathias Picker	27e74c4df7	docs: add auto-generated browser support page (#18276) ... ## Summary Adds a [Browser support](https://github.com/MathiasWP/svelte/blob/document-pipeline-draft/documentation/docs/07-misc/05-browser-support.md) page listing the minimum browser versions Svelte's runtime and compiler output require. The page (headline floor + per-feature requirements) is auto-generated by `packages/svelte/scripts/generate-browser-support.js`, which scans the code Svelte actually ships against the [web-features](https://github.com/web-platform-dx/web-features) Baseline dataset and resolves results to concrete browser versions via [baseline-browser-mapping](https://github.com/web-platform-dx/baseline-browser-mapping). CI fails if a PR moves the floor without regenerating the page. For 5.55.9 the floor is **Baseline 2020**: Chrome/Edge 87, Firefox 83, Safari 14. ## How it works 1. **Headline floor.** Each runtime entry from `pkg.exports` is bundled with rollup using production conditions, then walked with TypeScript's compiler API + TypeChecker. The walker (`browser-support.detector.js`) flags any web-features ID the runtime references; the highest Baseline year among them is the floor. 2. **Per-feature requirements.** Every user-facing surface is enumerated programmatically — every `bind:*` from `binding_properties`, every public subpackage export discovered via `pkg.exports` + `import * as ns`, every rune from `RUNES`, and directives (`transition:` / `animate:` / `use:` / `@attach` / `{@html}` / custom elements). Each gets a fixture, compiled and bundled like user code, then scanned. A row appears only when the fixture's floor exceeds the runtime floor. 3. **Supplemental rules.** A handful of APIs `web-features` doesn't catalogue (`getComputedStyle(...).zoom`, `box: 'device-pixel-content-box'`) are detected with the same type-aware walker via a small `register_extra_rules` list with inline justifications. 4. **Ignore sets.** `SAFE_TO_IGNORE` covers dataset bugs and feature-detected APIs with graceful fallbacks. `BEHAVIORAL_IGNORE` hides APIs reached only via specific user code from the headline (they still surface as conditional rows); staleness-checked, so CI fails if an entry no longer exists in the runtime. Resolves #18198. Provides an answer to the long-standing #558. ## Test plan - [ ] \`pnpm --filter svelte generate:browser-support\` regenerates the page idempotently - [ ] CI fails when a code change bumps the floor without regenerating the page - [ ] Page renders correctly on svelte.dev 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com> Co-authored-by: Rich Harris <rich.harris@vercel.com>	2 months ago
Paolo Ricciuti	516973c320	chore: replace custom renderer type arguments with a single one (#18244) ... Alternative to #18216 Allows for inference to still works but also allow for explicit declaration in the cases where it's needed. I made some changes to the code proposed by @mrkishi (I used `unique symbol` for the `DefaultType`, inferred the `NodeType`) but overall is mostly his work. I've also replaced the renderer for the test with a `TS` version of it so we can better test the types there. I think this is the best middle ground solution...inference works (when it works...we can document that you need to put the create methods first and the gotchas of automatic inference) but people can also quickly specify their types in an object.	2 months ago
Mathias Picker	67090e8ee8	perf: store current_sources as Set for O(1) membership checks (#18278) ... `current_sources` tracks the sources created within the active reaction so that reading or writing them during that same reaction doesn't trigger a re-run. It was an `Array` checked with `Array.prototype.includes.call(...)` in three hot places: the `state_unsafe_mutation` guard, `set()`'s destruction check, and `schedule_possible_effect_self_invalidation`. --------- Co-authored-by: Rich Harris <rich.harris@vercel.com>	2 months ago
paoloricciuti	4fb6b2fc9a	fix: special case `init_operations` check-treeshakeability	2 months ago
Paolo Ricciuti	91563f0b04	Merge branch 'main' into svelte-custom-renderer	2 months ago
github-actions[bot]	0bb715d3cf	Version Packages (#18255) ... This PR was opened by the [Changesets release](https://github.com/changesets/action) GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated. # Releases ## svelte@5.55.10 ### Patch Changes - fix: unlink errored and otherwise finished batch ([#18264](https://github.com/sveltejs/svelte/pull/18264)) - perf: walk composedPath() directly in delegated event propagation ([#18268](https://github.com/sveltejs/svelte/pull/18268)) - fix: transfer effects when merging batches ([#18254](https://github.com/sveltejs/svelte/pull/18254)) - fix: allow `$derived(await ...)` in disconnected effect roots ([#18273](https://github.com/sveltejs/svelte/pull/18273)) - fix: remove temporary raw-text hydration markers ([#18269](https://github.com/sveltejs/svelte/pull/18269)) - fix: propagate async `@const` blockers through closure references so template expressions like `{(() => host)()}` correctly wait for the awaited value ([#18309](https://github.com/sveltejs/svelte/pull/18309)) - fix: properly unlink batches ([#18298](https://github.com/sveltejs/svelte/pull/18298)) - fix: settle discarded batch ([#18290](https://github.com/sveltejs/svelte/pull/18290)) - fix: declare `let:` directives before `{@const}` declarations on slotted elements ([#18271](https://github.com/sveltejs/svelte/pull/18271)) - fix: resume outro-ed branches if they were kept around ([#18291](https://github.com/sveltejs/svelte/pull/18291)) - fix: avoid waterfall-warning when async resolves to same value ([#18297](https://github.com/sveltejs/svelte/pull/18297)) - fix: correctly coordinate component-level effects inside async blocks ([#18260](https://github.com/sveltejs/svelte/pull/18260)) - fix: make unnecessary commit work less likely ([#18263](https://github.com/sveltejs/svelte/pull/18263)) - chore: add tag name to `a11y_click_events_have_key_events` warning ([#18272](https://github.com/sveltejs/svelte/pull/18272)) - fix: catch rejected promises while merging/committing ([#18266](https://github.com/sveltejs/svelte/pull/18266)) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>	2 months ago
Rich Harris	688671ec23	chore: fix printing in sandbox (#18311) ... when `PRINT` is true, the sandbox should write out the printed code. at present it doesn't do this if `AST` is not also true	2 months ago
Simon H	4953860835	chore: remove unused class property (#18307) ... remnant of blocker approach	2 months ago
Simon H	638ab370a5	fix: prevent batch unlinking twice (#18303) ... Merged #18298 a bit too soon - there's still a situation which can corrput the linked list: If we merge one batch into another, it will unlink the batch immediately. But `discard` also calls it, running the unlink logic again, which can corrupt the linked list. Sketch: 1. Batch A is pending. 2. Batch B starts later, intersects A, resolves first, and merges into A. 3. B is unlinked immediately, but `A.oncommit(() => B.discard())` remains. 4. Independent batch C is created while A is still pending and is linked after A. 5. A commits, calls `B.discard()`, and B's stale `#prev`/`#next` can set `A.#next = null` / `last_batch = A`, disconnecting C. Not able to produce a failing test from it but it's definitely a fix we need to make. Also moved `#link` into a constructor, because it is (and should be) used only once. Also made the action after an error `discard` instead of just `#unlink` because this batch is done for and e.g. pending `settled` should resolve, too.	2 months ago
Rich Harris	0da9f9e2ab	fix: disallow effect creation after `await` (#18299) ... We incorrectly restore effect context after an`$derived(await ...)` if it occurs inside an async function, but only for those, no other `await` expressions. This is buggy and wrong. We only want to restore context _inside_ an async derived expression (including template expressions)` so that `await a + b` works correctly. It's possible that this will be a breaking change (albeit not semver-violating, because `experimental`) for some people if they are creating effects after an `await` (other than at the top level of a component). This is regrettable, but it should never have worked in the first place.	2 months ago
Simon H	d4be4e2973	chore: ensure treeshaking test runs during CI (#18302) ... Would've caught the regression in #18250 - without this the tests were all green, giving a false sense of "this is correct"	2 months ago
Paolo Ricciuti	203fe2e62e	Merge branch 'main' into svelte-custom-renderer	2 months ago
Elliott Johnson	e705369dee	fix: propagate async @const blockers through closure references (#18309) ... Right now, if you have the following: ```svelte {@const data = await foo} <p>{(() => data)()}<p> ``` It will blow up during CSR, because it tries to read `data` before it exists. The solution to this is to consider references inside closures as blockers for those closures. This _does_ mean we'll overblock in some circumstances, such as: ```svelte {@const data = await foo} <button onclick={() => data}>foo<button> ``` But I wonder if that's actually incorrect? If the user were to click `onclick` before `data` is ready, it would blow up. --------- Co-authored-by: Rich Harris <rich.harris@vercel.com>	2 months ago
Paolo Ricciuti	a8296352a1	Merge branch 'main' into svelte-custom-renderer	2 months ago
Rich Harris	ec08dbc7ee	fix: only unlink batch if we're done with it (#18298) ... alternative to #18296 — no need to make batches relinkable if we only unlink them when we're fully done with them	2 months ago
Simon H	b40c359d44	fix: don't assume boundary exists during increment/decrement (#18289) ... Follow-up to #18273 (not merged yet hence no changeset here): We can run into a null-pointer when wanting to increment/decrement inside an effect root that is outside a the component tree. Similarly, if not using the component logic to unset context at the right time we gotta do it "manually" inside `save`. --------- Co-authored-by: Rich Harris <rich.harris@vercel.com> Co-authored-by: vercel[bot] <35613825+vercel[bot]@users.noreply.github.com>	2 months ago
Simon H	c01e598fff	fix: avoid waterfall-warning when async resolves to same value (#18297)	2 months ago
Rich Harris	070a0c4f77	Revert "perf: use Set instead of Array for constant lookups in utils.js" (#18294) ... Reverts sveltejs/svelte#18250	2 months ago
Rich Harris	c9f7298270	chore: fix spelling in test (#18292) ... ugh i forgot to approve workflows in slop PR #18281 and now tests are failing	2 months ago
RonGamzu	d2c7fa3494	fix: use consistent spelling in script_unknown_attribute warning (#18281) ... ## Summary The `script_unknown_attribute` warning message used American English (`Unrecognized`) while every other user-facing error/warning in the compiler uses British English (`Unrecognised`): - `options_unrecognised` error: `Unrecognised compiler option…` - `unknown_code` warning: `is not a recognised code` This change updates `script_unknown_attribute` to match, then regenerates `warnings.js` and the reference documentation from the source message file via `node scripts/process-messages`. ## Test plan - Spelling change is isolated to the `script_unknown_attribute` warning message - `warnings.js` and generated docs were updated by running `node scripts/process-messages` - All three occurrences (source, generated JS, generated docs) are consistent	2 months ago
Simon H	60eaa92b0b	fix: resume outro-ed branches if they were kept around (#18291) ... If a branch is removed from the visible dom, it may be kept around because a subsequent batch will intro it again. If we don't resume the effects it will stay inert and therefore not react to updates anymore	2 months ago
Simon H	871e590c59	fix: settle discarded batch (#18290) ... Without this the promise would never resolve	2 months ago
Mathias Picker	e6110d31c5	perf: use Set instead of Array for constant lookups in utils.js (#18250) ... Several constant lookup tables in `utils.js` were arrays searched with `Array.prototype.includes`, which is O(n). They're queried often — per attribute during attribute setup and SSR, per event during event delegation, and per identifier during compilation. Switching them to `Set` makes each lookup O(1) without changing any public behaviour.	2 months ago
paoloricciuti	d8f94880fb	chore: merge	2 months ago
Simon H	fe9ab936b6	fix: allow `$derived(await ...)` in disconnected effect roots (#18273) ... If `$effect.root` is created outside the component tree, the boundary property is null Fixes #18188	2 months ago
Karl Georgsen	f023e8d7c8	chore: add tag name to a11y_click_events_have_key_events warning (#18272) ... Ref: https://github.com/sveltejs/svelte/issues/15100 Adds the tag name to the `a11y_click_events_have_key_events` warning given when a non-interactive element has a click handler but no keyboard events. This already happens in `a11y_no_static_element_interactions`, and should probably happen in many more messages.	2 months ago
wheelman	bb69f9c44c	fix: declare `let:` directives before `{@const}` on slotted elements (#18271) ... Fixes #18119 (missed a spot in #16985)	2 months ago
Puneet Dixit	8b961be0b1	fix: remove raw-text hydration markers (#18269) ... Fixes #14413. This keeps the temporary raw-text hydration sentinel used by dynamic `<svelte:element>` from becoming part of the final DOM. Hydration still gets a marker to advance through for raw-text children, but the marker is removed after the child renderer runs, so `<style>` and `<script>` contents stay identical to SSR output. Tests: - `pnpm test hydration -t svelte-head-dynamic-style` - `pnpm test hydration` - `pnpm test runtime-runes -t svelte-element` - `pnpm lint` - `git diff --check` --------- Co-authored-by: Puneet Dixit <236133619+puneetdixit200@users.noreply.github.com> Co-authored-by: Simon H <5968653+dummdidumm@users.noreply.github.com>	2 months ago
Mathias Picker	04d408b29d	perf: walk composedPath() directly in delegated event propagation (#18268) ... ## Summary The propagation walk in `handle_event_propagation` already calls `event.composedPath()` at the start to find the entry index, but then re-derives the same chain step-by-step via `current_target.assignedSlot || current_target.parentNode || .host`. Three property reads per iteration is measurable on the hot event path. Walk the captured `path` array by index instead. ## Notes on behavior `composedPath()` is the spec-compliant snapshot of the dispatch chain: - Same shadow-DOM crossings (slots and shadow roots are included for composed events). - Same `host` traversal (composed-path crosses shadow boundaries when appropriate). - Differs from the previous walk in one edge case: if a handler removes a parent mid-dispatch, the snapshot-based walk continues through the captured chain (matches native browser semantics — the previous `parentNode` walk would have stopped at a null parent). ## Performance Measured in real Chromium on a click through a 30-deep tree with five delegated handlers: **~245k hz → ~277k hz** (~+13%, ~−12% per-event time). ## Test plan - [x] All 6006 runtime tests pass (runtime-runes + runtime-legacy + runtime-browser) - [x] Native shadow-DOM event tests (in runtime-browser) pass unchanged 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2 months ago
Simon H	078f901f61	fix: catch rejected promises while merging/committing (#18266) ... A committing/merging batch can have promises that were rejected (e.g. as obsolete). We gotta "forward" this rejection, too, instead of just the successful promise. At best it results in a uncaught rejection (`async-branch-merge-obsolete`), at worst it means error boundaries are not correctly displayed (`async-later-promise-fails-first`). Solves the reproduction in https://github.com/sveltejs/svelte/issues/18221#issuecomment-4507803845	2 months ago
Simon H	a6002b587c	fix: unlink errored and otherwise finished batch (#18264) ... This fixes the issue in https://github.com/sveltejs/svelte/issues/18221#issuecomment-4497918414 where an error can create follup-up invariant errors. The batch errors, has no chance to run otherwise (no more pending work) and is therefore "dead". That means we need to unlink it otherwise it's becoming a "zombie" and hangs around, causing unnecessary and potentially buggy (as seen in the reproduction) merge/commit work. I was not able to reduce the reproduction down to a test case that fails without the fix, but it does make a related error test from #17888 work more correctly.	2 months ago
Simon H	4656e6895d	fix: make unnecessary commit work less likely (#18263) ... While looking at https://github.com/sveltejs/svelte/issues/18221#issuecomment-4497918414 and trying to understand how the invariant can happen I noticed that we are not correctly filtering during commit. - we were not ignoring deriveds - we were not comparing the correct values (checking `source.v` instead of the saved value) and not checking if their "is a derived" state differs I'm not able to come up with a test where something fails without these (possibly because it's more about an optimization to do less reruns and not about correctness) fixes, but they do make sense.	2 months ago
Simon H	91a42e2ed6	fix: correctly coordinate component-level effects inside async blocks (#18260) ... While looking at the reproduction in https://github.com/sveltejs/svelte/issues/18221#issuecomment-4497918414 I immediately got greeted with a runtime error when running it in the playground (weirdly not in the Stackblitz version). The error was that a component expected a binding to be set in onMount, but the timing of onMount was wrong. Turns out it's because our logic to determine whether or not to defer top level effects is flawed. `REACTION_RAN`, which was used previously, is already set if the initialized component is inside an async block. We instead check for `component_context.i` which is set to `true` on `pop()`.	2 months ago
Simon H	65283bc13a	fix: transfer effects when merging batches (#18254) ... An effect could be gated behind a branch. If we don't defer + transfer them upon merge, the branch would still be marked clean but the effect behind it is dirty but no longer reachable. It's not reachable via mark either because that one only concerns itself with block/async effects, and the branch gating the effect is not guaranteed to be touched by that. Fixes #18249 Little sad side-effect: Since we cannot reliably know _before_ traversal if we have no blocking pending work left (the traversal could mark an if block falsy which contains the last blocker), we gotta undo a performance optimization.	2 months ago
Paolo Ricciuti	078a77c9ad	Merge branch 'main' into svelte-custom-renderer	2 months ago
github-actions[bot]	b65a3f3fc5	Version Packages (#18240) ... This PR was opened by the [Changesets release](https://github.com/changesets/action) GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated. # Releases ## svelte@5.55.9 ### Patch Changes - fix: don't unset batch when calling `{#await ...}` promise ([#18243](https://github.com/sveltejs/svelte/pull/18243)) - fix: promise-ify `{#await await ...}` expressions on the server and correctly hydrate them on the client ([#18243](https://github.com/sveltejs/svelte/pull/18243)) - fix: deduplicate dependencies that are added outside the init/update cycle ([#18243](https://github.com/sveltejs/svelte/pull/18243)) - fix: avoid false-positive batch invariant error ([#18246](https://github.com/sveltejs/svelte/pull/18246)) - fix: inline primitive constants in attribute values during SSR ([#18232](https://github.com/sveltejs/svelte/pull/18232)) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>	2 months ago