Skip to content

build(deps): bump the major group across 1 directory with 9 updates - #41

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/major-cdab11e620
Open

build(deps): bump the major group across 1 directory with 9 updates#41
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/major-cdab11e620

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Sep 1, 2026

Copy link
Copy Markdown

Bumps the major group with 9 updates in the / directory:

Package From To
jsdom 29.1.1 30.0.1
@types/jsdom 28.0.3 30.0.0
@changesets/changelog-github 0.7.0 1.0.0
@changesets/cli 2.31.0 3.0.1
@marko/vite 5.4.10 6.1.11
@testing-library/jest-dom 6.9.1 7.0.1
eslint-plugin-simple-import-sort 13.0.0 14.0.0
marko 5.39.13 6.3.46
typescript 6.0.3 7.0.2

Updates jsdom from 29.1.1 to 30.0.1

Release notes

Sourced from jsdom's releases.

v30.0.1

  • Fixed getComputedStyle() with calc() and other functions throwing an exception, which regressed in v30.0.0. (@​asamuzaK)
  • Sped up up range operations on large documents (@​leonidaz)

v30.0.0

Breaking changes:

  • Node.js minimum version raised to ^22.22.2 || ^24.15.0 || >=26.0.0.

Other changes:

  • Added CSS.escape() and CSS.supports() functions. (@​asamuzaK)
  • Added 'background-position-x' and 'background-position-y' CSS properties. (@​olagokemills)
  • Fixed getComputedStyle() to convert length values into pixels. (@​asamuzaK)
  • Fixed CSS function serialization, e.g., in the return value of getPropertyValue(). (@​asamuzaK)
  • Fixed the type of error thrown by document.evaluate() (@​dokson)
Commits
  • 6584485 30.0.1
  • 0c51df6 Update dependencies and dev dependencies
  • 32adb34 Bump @​asamuzakjp/dom-selector
  • 70f014a Speed up range operations on large documents
  • 250d7ee Partially fix getComputedStyle with calc()
  • 20a01fc 30.0.0
  • 8c8e583 Precompute WPT expectation matches
  • f32245c Bump Node.js floor and dependencies
  • 03ef23b Add background-position longhands
  • ded056f Test CSS.escape() with numeric IDs
  • Additional commits viewable in compare view

Updates @types/jsdom from 28.0.3 to 30.0.0

Commits

Updates @changesets/changelog-github from 0.7.0 to 1.0.0

Release notes

Sourced from @​changesets/changelog-github's releases.

@​changesets/changelog-github@​1.0.0

Major Changes

Minor Changes

  • #2059 070f531 Thanks @​jycouet! - Add an opt-in, experimental template option to render changelog lines from tokens ({summary}, {ref}, {pull}, {commit}, {authors}). Default output is unchanged. The token syntax may change in a patch release; pin the version if you rely on it.

  • #1871 dfefc4e Thanks @​mihkeleidast! - Use GITHUB_REPOSITORY as the default repo when no repo option is configured

  • #1969 2c7c043 Thanks @​marcalexiei! - Add a named export that mirrors the current default export

    The default export is slated for removal in the next major release, so this ensures a smoother transition path.

Patch Changes

@​changesets/changelog-github@​1.0.0-next.9

Patch Changes

  • Updated dependencies [96b65ee]:
    • @​changesets/types@​7.0.0-next.9

@​changesets/changelog-github@​1.0.0-next.3

Major Changes

Minor Changes

  • #1969 2c7c043 Thanks @​marcalexiei! - Add a named export that mirrors the current default export

    The default export is slated for removal in the next major release, so this ensures a smoother transition path.

Patch Changes

... (truncated)

Changelog

Sourced from @​changesets/changelog-github's changelog.

1.0.0

Major Changes

Minor Changes

  • #2059 070f531 Thanks @​jycouet! - Add an opt-in, experimental template option to render changelog lines from tokens ({summary}, {ref}, {pull}, {commit}, {authors}). Default output is unchanged. The token syntax may change in a patch release; pin the version if you rely on it.

  • #1871 dfefc4e Thanks @​mihkeleidast! - Use GITHUB_REPOSITORY as the default repo when no repo option is configured

  • #1969 2c7c043 Thanks @​marcalexiei! - Add a named export that mirrors the current default export

    The default export is slated for removal in the next major release, so this ensures a smoother transition path.

Patch Changes

1.0.0-next.9

Patch Changes

  • Updated dependencies [96b65ee]:
    • @​changesets/types@​7.0.0-next.9

1.0.0-next.8

Patch Changes

  • Updated dependencies [b5e1762]:
    • @​changesets/types@​7.0.0-next.8

1.0.0-next.7

Patch Changes

  • #2160 162419d Thanks @​beeequeue! - Added or modified the files property in the manifest. This should not change any behavior.
  • Updated dependencies [162419d]:
    • @​changesets/get-github-info@​1.0.0-next.4

... (truncated)

Commits

Updates @changesets/cli from 2.31.0 to 3.0.1

Release notes

Sourced from @​changesets/cli's releases.

@​changesets/cli@​3.0.1

Patch Changes

@​changesets/cli@​3.0.0

Major Changes

  • #2128 7113c01 Thanks @​Andarist! - Renamed the changeset tag command to changeset git-tag.

  • #2074 3599e47 Thanks @​bluwy! - Set supported package manager versions in "engines" field, including npm >=10.9.0, pnpm >=10.0.0, and yarn >=4.5.2.

  • #1860 92b1c1b Thanks @​mixelburg! - changeset version now exits with code 1 when there are no unreleased changesets, instead of silently exiting with code 0.

    This makes it easier to detect when a version step is a no-op — for example, to prevent accidentally publishing packages with incorrect version tags when using --snapshot mode.

  • #1482 df424a4 Thanks @​Andarist! - Bumped supported Node versions to ^22.11 || ^24 || >=26

  • #1994 062530b Thanks @​bluwy! - The prettier option in .changeset/config.json has been removed in favor of format. format supports "auto", "prettier", "oxfmt", "deno", and "dprint", and false disables formatting. If you previously used prettier: false, migrate to format: false or remove the option to use automatic formatter detection.

  • #2190 96b65ee Thanks @​bluwy! - Move versioned prerelease changesets to .changeset/pre/ folder instead of accumulating in the root and tracking the versioned changeset ids in the .changeset/pre.json file. Existing pre.json will auto-migrate to this new structure on the next run of changeset version or when calling changeset status.

    This change allows easier management of versioned prerelease changesets (for the final stable release) and current queued changesets (for the next prerelease). Changesets in .changeset/pre/ can be edited or deleted depending if it's still relevant for the final stable release of a package. There's no need to synchronize the changeset ids in pre.json if certain changesets are deleted.

  • #2145 f5887ff Thanks @​Andarist! - Removed Yarn Classic support

  • #2097 8c88f6a Thanks @​Andarist! - Packages with only prerelease versions published will now be published with the prerelease tag in the prerelease mode if the target registry doesn't auto-assign latest tag. npm registry itself does that and such packages will continue to be released with latest tag (and not with the configured prerelease tag).

  • #1879 c76b232 Thanks @​beeequeue! - Removed warning messages about using v1 configs. They will now be silently ignored.

  • #1655 db46911 Thanks @​bluwy! - Update @manypkg/get-packages which drops support for detecting packages in Bolt monorepos and adds support for npm monorepos

  • #1651 e1df862 Thanks @​bluwy! - Remove support for the --sinceMaster flag for changeset status. Use --since=master or --since=main instead.

  • #2117 813bbf3 Thanks @​bluwy! - Remove the pre.json initialVersions property and handling as it's unused internally

  • #1961 07278a7 Thanks @​beeequeue! - CommitFunctions can now be both sync and async, and the defaultCommitFunctions are now sync.

  • #1482 df424a4 Thanks @​Andarist! - From now on this package is going to be published as ES module.

  • #1652 a0b5326 Thanks @​bluwy! - Remove support for the deprecated ___experimentalUnsafeOptions_WILL_CHANGE_IN_PATCH.useCalculatedVersionForSnapshots config. The snapshot.useCalculatedVersion config should be used instead.

  • #2186 3910adf Thanks @​Andarist! - Private packages are no longer versioned by default. Set privatePackages to true to opt into versioning and tagging them, or set privatePackages.version to true to version them without tagging.

  • #1879 c76b232 Thanks @​beeequeue! - Migrated from enquirer + @inquirer/launch-editor to @clack/prompts + launch-editor.

    This means the CLI flows will have minor changes, but they are largely the same.

... (truncated)

Changelog

Sourced from @​changesets/cli's changelog.

3.0.1

Patch Changes

3.0.0

Major Changes

  • #2128 7113c01 Thanks @​Andarist! - Renamed the changeset tag command to changeset git-tag.

  • #2074 3599e47 Thanks @​bluwy! - Set supported package manager versions in "engines" field, including npm >=10.9.0, pnpm >=10.0.0, and yarn >=4.5.2.

  • #1860 92b1c1b Thanks @​mixelburg! - changeset version now exits with code 1 when there are no unreleased changesets, instead of silently exiting with code 0.

    This makes it easier to detect when a version step is a no-op — for example, to prevent accidentally publishing packages with incorrect version tags when using --snapshot mode.

  • #1482 df424a4 Thanks @​Andarist! - Bumped supported Node versions to ^22.11 || ^24 || >=26

  • #1994 062530b Thanks @​bluwy! - The prettier option in .changeset/config.json has been removed in favor of format. format supports "auto", "prettier", "oxfmt", "deno", and "dprint", and false disables formatting. If you previously used prettier: false, migrate to format: false or remove the option to use automatic formatter detection.

  • #2190 96b65ee Thanks @​bluwy! - Move versioned prerelease changesets to .changeset/pre/ folder instead of accumulating in the root and tracking the versioned changeset ids in the .changeset/pre.json file. Existing pre.json will auto-migrate to this new structure on the next run of changeset version or when calling changeset status.

    This change allows easier management of versioned prerelease changesets (for the final stable release) and current queued changesets (for the next prerelease). Changesets in .changeset/pre/ can be edited or deleted depending if it's still relevant for the final stable release of a package. There's no need to synchronize the changeset ids in pre.json if certain changesets are deleted.

  • #2145 f5887ff Thanks @​Andarist! - Removed Yarn Classic support

  • #2097 8c88f6a Thanks @​Andarist! - Packages with only prerelease versions published will now be published with the prerelease tag in the prerelease mode if the target registry doesn't auto-assign latest tag. npm registry itself does that and such packages will continue to be released with latest tag (and not with the configured prerelease tag).

  • #1879 c76b232 Thanks @​beeequeue! - Removed warning messages about using v1 configs. They will now be silently ignored.

  • #1655 db46911 Thanks @​bluwy! - Update @manypkg/get-packages which drops support for detecting packages in Bolt monorepos and adds support for npm monorepos

  • #1651 e1df862 Thanks @​bluwy! - Remove support for the --sinceMaster flag for changeset status. Use --since=master or --since=main instead.

  • #2117 813bbf3 Thanks @​bluwy! - Remove the pre.json initialVersions property and handling as it's unused internally

  • #1961 07278a7 Thanks @​beeequeue! - CommitFunctions can now be both sync and async, and the defaultCommitFunctions are now sync.

  • #1482 df424a4 Thanks @​Andarist! - From now on this package is going to be published as ES module.

  • #1652 a0b5326 Thanks @​bluwy! - Remove support for the deprecated ___experimentalUnsafeOptions_WILL_CHANGE_IN_PATCH.useCalculatedVersionForSnapshots config. The snapshot.useCalculatedVersion config should be used instead.

  • #2186 3910adf Thanks @​Andarist! - Private packages are no longer versioned by default. Set privatePackages to true to opt into versioning and tagging them, or set privatePackages.version to true to version them without tagging.

  • #1879 c76b232 Thanks @​beeequeue! - Migrated from enquirer + @inquirer/launch-editor to @clack/prompts + launch-editor.

... (truncated)

Commits

Updates @marko/vite from 5.4.10 to 6.1.11

Release notes

Sourced from @​marko/vite's releases.

v6.1.11

Patch Changes

  • #308 b7b91e0 Thanks @​DylanPiercey! - Only apply the client build's side effect free default when linked. Unlinked consumers such as Storybook and vitest supply their own entries, whose modules run for their side effects, so tree-shaking them broke those setups (eg a static Storybook lost the addon channel setup and composed refs never finished loading).

v6.1.10

Patch Changes

  • #305 c1b1bfb Thanks @​DylanPiercey! - Treat zero-runtime stylesheet modules (*.css.ts, *.css.js) as having side effects so their styles are still emitted when only server-rendered markup uses them.

v6.1.9

Patch Changes

  • #302 0a401ca Thanks @​DylanPiercey! - Fix a crash when vitest resolves a vite config that has no test section. The plugin read config.test.environment unguarded in test mode, so simply having @marko/vite installed made vitest run fail before any test loaded.

v6.1.8

Patch Changes

  • #299 6228f86 Thanks @​DylanPiercey! - Compile .marko modules whose id carries an unrecognized query, such as the marker @vitest/coverage-* appends when it pulls in files no test imported, which previously reached the coverage instrumenter as uncompiled Marko source. Queries that change what the module is (?raw, ?url, ?inline, ...) are still left for vite to serve.

v6.1.7

Patch Changes

  • #297 b73226a Thanks @​DylanPiercey! - Stop following symlinks when discovering known templates for optimized builds: pnpm layouts link node_modules as cyclic symlink graphs, so the walk previously never terminated and exhausted the heap.

v6.1.6

Patch Changes

  • #293 b44290d Thanks @​DylanPiercey! - Require marko@5.39.14 for the class runtime's linkAssets/entry support. Older versions' generated withPageAssets page entry ignored a configured runtimeId, so the server serialized hydration data under the default $MC key while the client entry read $<runtimeId>_C and never hydrated (for example, onMount never firing). Older class runtimes now fall back to the legacy asset orchestration, which honors the runtimeId.

v6.1.5

Patch Changes

  • #291 dc6d57b Thanks @​DylanPiercey! - Fix a spurious Sourcemap for "\<template>.marko-virtual.scss" points to missing source files warning in dev when a .marko template has a <style> block. The dep optimizer compiled templates with sourceMaps: "inline", which drops the extracted style block's separate sourcemap; the shared compiler cache then left the dev server serving the virtual CSS with no map to trace back to its template, so the style preprocessor emitted a self-referential map to the (non-existent) virtual file. The optimizer now uses sourceMaps: "both" so the separate map is retained, and the entry compile configs no longer force sourceMaps: false (the compiler now skips the entry wrapper's own map on its side), so CSS sourcemaps survive.

v6.1.4

Patch Changes

v6.1.3

Patch Changes

  • #286 22a4f80 Thanks @​DylanPiercey! - Carry a template's explicit bare import "x" side effect marking downstream to the modules x itself imports. Previously only x was exempt from the client build's side effect free default, so a package whose effect lives in a module it bare-imports (eg terser installing AST_Toplevel#resolve_defines from import "./global-defs.js") still had that module shaken out. Marko files, styles and assets remain non-propagating, so a template's own imports stay shakeable.

v6.1.2

Patch Changes

  • #283 db7ee41 Thanks @​DylanPiercey! - When a coding agent is driving the terminal (detected via the env markers agents set, e.g. CLAUDECODE, CURSOR_AGENT, GEMINI_CLI, AI_AGENT) and the installed marko package ships an LLM syntax reference, compile errors now end with a fix-guide pointer: "Fix guide: READ node_modules/marko/cheatsheet.md before writing a fix." Projects whose marko version does not ship cheatsheet.md — and all human-driven terminals — are unaffected.

... (truncated)

Changelog

Sourced from @​marko/vite's changelog.

6.1.11

Patch Changes

  • #308 b7b91e0 Thanks @​DylanPiercey! - Only apply the client build's side effect free default when linked. Unlinked consumers such as Storybook and vitest supply their own entries, whose modules run for their side effects, so tree-shaking them broke those setups (eg a static Storybook lost the addon channel setup and composed refs never finished loading).

6.1.10

Patch Changes

  • #305 c1b1bfb Thanks @​DylanPiercey! - Treat zero-runtime stylesheet modules (*.css.ts, *.css.js) as having side effects so their styles are still emitted when only server-rendered markup uses them.

6.1.9

Patch Changes

  • #302 0a401ca Thanks @​DylanPiercey! - Fix a crash when vitest resolves a vite config that has no test section. The plugin read config.test.environment unguarded in test mode, so simply having @marko/vite installed made vitest run fail before any test loaded.

6.1.8

Patch Changes

  • #299 6228f86 Thanks @​DylanPiercey! - Compile .marko modules whose id carries an unrecognized query, such as the marker @vitest/coverage-* appends when it pulls in files no test imported, which previously reached the coverage instrumenter as uncompiled Marko source. Queries that change what the module is (?raw, ?url, ?inline, ...) are still left for vite to serve.

6.1.7

Patch Changes

  • #297 b73226a Thanks @​DylanPiercey! - Stop following symlinks when discovering known templates for optimized builds: pnpm layouts link node_modules as cyclic symlink graphs, so the walk previously never terminated and exhausted the heap.

6.1.6

Patch Changes

  • #293 b44290d Thanks @​DylanPiercey! - Require marko@5.39.14 for the class runtime's linkAssets/entry support. Older versions' generated withPageAssets page entry ignored a configured runtimeId, so the server serialized hydration data under the default $MC key while the client entry read $<runtimeId>_C and never hydrated (for example, onMount never firing). Older class runtimes now fall back to the legacy asset orchestration, which honors the runtimeId.

6.1.5

Patch Changes

  • #291 dc6d57b Thanks @​DylanPiercey! - Fix a spurious Sourcemap for "\<template>.marko-virtual.scss" points to missing source files warning in dev when a .marko template has a <style> block. The dep optimizer compiled templates with sourceMaps: "inline", which drops the extracted style block's separate sourcemap; the shared compiler cache then left the dev server serving the virtual CSS with no map to trace back to its template, so the style preprocessor emitted a self-referential map to the (non-existent) virtual file. The optimizer now uses sourceMaps: "both" so the separate map is retained, and the entry compile configs no longer force sourceMaps: false (the compiler now skips the entry wrapper's own map on its side), so CSS sourcemaps survive.

6.1.4

Patch Changes

6.1.3

... (truncated)

Commits

Updates @testing-library/jest-dom from 6.9.1 to 7.0.1

Release notes

Sourced from @​testing-library/jest-dom's releases.

v7.0.1

7.0.1 (2026-08-09)

Bug Fixes

  • declare vitest as an optional peer dependency (#733) (3782c78)

v7.0.0

7.0.0 (2026-07-20)

Features

  • add toContainAnyBy* and toContainOneBy* query matchers (1e39089)

BREAKING CHANGES

  • @​testing-library/dom is now a required peer dependency. The minimum supported Node.js version is now 22.

Repaired release for testing-library/jest-dom#731

v6.10.0

6.10.0 (2026-07-20)

Features

  • add toContainAnyBy* and toContainOneBy* query matchers (#731) (cae44df)
Commits
  • 3782c78 fix: declare vitest as an optional peer dependency (#733)
  • 1e39089 feat: add toContainAnyBy* and toContainOneBy* query matchers
  • cae44df feat: add toContainAnyBy* and toContainOneBy* query matchers (#731)
  • 55c07ce ci: switch release to npm trusted publishing (#726)
  • 213256f docs: move toHaveSelection from the deprecated section (#717)
  • See full diff in compare view
Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for @​testing-library/jest-dom since your current version.


Updates @types/jsdom from 28.0.3 to 30.0.0

Commits

Updates eslint-plugin-simple-import-sort from 13.0.0 to 14.0.0

Changelog

Sourced from eslint-plugin-simple-import-sort's changelog.

Version 14.0.0 (2026-07-16)

ES2022 allows string literals as module export names ("arbitrary module namespace names"):

export { yukuTs as "yuku-ts" };
import { "a-b" as c } from "a";

This release adds support for such quotes names. Previously, those were sorted oddly, and the autofix could suggest changes that wasn’t valid syntax.

This is only a breaking change if you use string literals as module export names, and only in the form of that you need to autofix your files.

Thanks to Kamronbek_Juraev (@​KAMRONBEK) for fixing this!

Commits

Bumps the major group with 9 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [jsdom](https://github.com/jsdom/jsdom) | `29.1.1` | `30.0.1` |
| [@types/jsdom](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/jsdom) | `28.0.3` | `30.0.0` |
| [@changesets/changelog-github](https://github.com/changesets/changesets/tree/HEAD/packages/changelog-github) | `0.7.0` | `1.0.0` |
| [@changesets/cli](https://github.com/changesets/changesets/tree/HEAD/packages/cli) | `2.31.0` | `3.0.1` |
| [@marko/vite](https://github.com/marko-js/vite) | `5.4.10` | `6.1.11` |
| [@testing-library/jest-dom](https://github.com/testing-library/jest-dom) | `6.9.1` | `7.0.1` |
| [eslint-plugin-simple-import-sort](https://github.com/lydell/eslint-plugin-simple-import-sort) | `13.0.0` | `14.0.0` |
| [marko](https://github.com/marko-js/marko/tree/HEAD/packages/runtime-tags) | `5.39.13` | `6.3.46` |
| [typescript](https://github.com/microsoft/TypeScript) | `6.0.3` | `7.0.2` |



Updates `jsdom` from 29.1.1 to 30.0.1
- [Release notes](https://github.com/jsdom/jsdom/releases)
- [Commits](jsdom/jsdom@v29.1.1...v30.0.1)

Updates `@types/jsdom` from 28.0.3 to 30.0.0
- [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases)
- [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/jsdom)

Updates `@changesets/changelog-github` from 0.7.0 to 1.0.0
- [Release notes](https://github.com/changesets/changesets/releases)
- [Changelog](https://github.com/changesets/changesets/blob/main/packages/changelog-github/CHANGELOG.md)
- [Commits](https://github.com/changesets/changesets/commits/@changesets/changelog-github@1.0.0/packages/changelog-github)

Updates `@changesets/cli` from 2.31.0 to 3.0.1
- [Release notes](https://github.com/changesets/changesets/releases)
- [Changelog](https://github.com/changesets/changesets/blob/main/packages/cli/CHANGELOG.md)
- [Commits](https://github.com/changesets/changesets/commits/@changesets/cli@3.0.1/packages/cli)

Updates `@marko/vite` from 5.4.10 to 6.1.11
- [Release notes](https://github.com/marko-js/vite/releases)
- [Changelog](https://github.com/marko-js/vite/blob/main/CHANGELOG.md)
- [Commits](https://github.com/marko-js/vite/commits/v6.1.11)

Updates `@testing-library/jest-dom` from 6.9.1 to 7.0.1
- [Release notes](https://github.com/testing-library/jest-dom/releases)
- [Changelog](https://github.com/testing-library/jest-dom/blob/main/CHANGELOG.md)
- [Commits](testing-library/jest-dom@v6.9.1...v7.0.1)

Updates `@types/jsdom` from 28.0.3 to 30.0.0
- [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases)
- [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/jsdom)

Updates `eslint-plugin-simple-import-sort` from 13.0.0 to 14.0.0
- [Changelog](https://github.com/lydell/eslint-plugin-simple-import-sort/blob/main/CHANGELOG.md)
- [Commits](lydell/eslint-plugin-simple-import-sort@v13.0.0...v14.0.0)

Updates `marko` from 5.39.13 to 6.3.46
- [Release notes](https://github.com/marko-js/marko/releases)
- [Changelog](https://github.com/marko-js/marko/blob/main/packages/runtime-tags/CHANGELOG.md)
- [Commits](https://github.com/marko-js/marko/commits/@marko/runtime-tags@6.3.46/packages/runtime-tags)

Updates `typescript` from 6.0.3 to 7.0.2
- [Release notes](https://github.com/microsoft/TypeScript/releases)
- [Commits](microsoft/TypeScript@v6.0.3...v7.0.2)

---
updated-dependencies:
- dependency-name: jsdom
  dependency-version: 30.0.1
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: major
- dependency-name: "@types/jsdom"
  dependency-version: 30.0.0
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: major
- dependency-name: "@changesets/changelog-github"
  dependency-version: 1.0.0
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: major
- dependency-name: "@changesets/cli"
  dependency-version: 3.0.1
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: major
- dependency-name: "@marko/vite"
  dependency-version: 6.1.11
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: major
- dependency-name: "@testing-library/jest-dom"
  dependency-version: 7.0.1
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: major
- dependency-name: "@types/jsdom"
  dependency-version: 30.0.0
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: major
- dependency-name: eslint-plugin-simple-import-sort
  dependency-version: 14.0.0
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: major
- dependency-name: marko
  dependency-version: 6.3.46
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: major
- dependency-name: typescript
  dependency-version: 7.0.2
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: major
...

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 Sep 1, 2026
@changeset-bot

changeset-bot Bot commented Sep 1, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: e1abce4

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

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.

0 participants