Skip to content

chore(deps)(deps): bump the minor-updates group across 1 directory with 13 updates - #38

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/minor-updates-acc1d86086
Open

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/minor-updates-acc1d86086

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Aug 30, 2026 •

Copy link
Copy Markdown
Contributor

Bumps the minor-updates group with 12 updates in the / directory:

Package From To
@stone-js/config 0.2.0 0.8.16
@stone-js/core 0.2.1 0.8.16
@stone-js/filesystem 0.1.2 0.8.16
@stone-js/node-cli-adapter 0.2.1 0.8.16
@stone-js/pipeline 0.1.3 0.8.16
@stone-js/router 0.2.2 0.8.16
@stone-js/use-react 0.3.1 0.8.16
fs-extra 11.3.5 11.4.0
rollup 4.61.1 4.63.0
rollup-plugin-dts 6.4.1 6.5.1
typedoc 0.28.19 0.28.20
typedoc-plugin-markdown 4.12.0 4.13.0

Updates @stone-js/config from 0.2.0 to 0.8.16

Changelog

Sourced from @​stone-js/config's changelog.

0.8.16

0.8.15

0.8.14

0.8.13

0.8.12

0.8.11

0.8.10

0.8.9

Patch Changes

  • 0629318: Point every README link at somewhere that exists.

    The per-module repositories were retired when the framework moved to a single one, so 36 links across 18 READMEs answered with a 404: the exact links a newcomer clicks first, "Contributing" and "API". The contributing guide now points at the monorepo, and the API reference at the published one.

    docs/ was never a durable target either, retired repository or not: it is TypeDoc output, and every build begins by deleting it.

  • f6d9fe4: fix(build): published declarations carry explicit .js extensions

    Our sources are bundler-style (extensionless relative imports) and tsc reproduces what they wrote. In a published ESM package with an exports map, a consumer on moduleResolution: nodenext cannot resolve those specifiers, so the types of everything they re-export become invisible. The reported symptom was misleading: error TS2305: Module '"@stone-js/use-react"' has no exported member 'useContainer', which reads as "the hook does not exist" rather than "the module was not resolved". A pilot project hit it on @stone-js/use-react and worked around it with moduleResolution: "bundler", which is right for bundled code but wrong for a pure Node ESM consumer.

    The shared build now rewrites relative specifiers in every emitted declaration (<file>.js, or <dir>/index.js for a directory), and the generated barrel emits them the same way. @stone-js/use-view, which carries its own rollup config, was wired to the same plugin.

    Verified across 635 declaration files: zero extensionless relative imports, and a moduleResolution: nodenext consumer importing useContainer / useBlueprint typechecks clean where it previously reported 138 errors. A pnpm run check:dts guard runs in CI right after the build so this cannot regress, including for a package that grows its own build config.

0.8.8

0.8.7

0.8.6

0.8.5

0.8.4

0.8.3

0.8.2

... (truncated)

Commits

Updates @stone-js/core from 0.2.1 to 0.8.16

Changelog

Sourced from @​stone-js/core's changelog.

0.8.16

Patch Changes

  • @​stone-js/pipeline@​0.8.16
  • @​stone-js/config@​0.8.16
  • @​stone-js/service-container@​0.8.16

0.8.15

Patch Changes

  • @​stone-js/pipeline@​0.8.15
  • @​stone-js/config@​0.8.15
  • @​stone-js/service-container@​0.8.15

0.8.14

Patch Changes

  • ed1bdb8: fix: an extension point can say which event it reads, and telemetry answers the probe

    SJ-44, and its family. IPolicy.authorize was a function-typed property with no type parameter, so narrowing it in an implementation was rejected (TS2416) and an application had to drop its implements clause. Swept every interface an application implements: IPolicy and IAuthorizer were exposed, ICommandHandler.match ignored the event type its own interface already carried, and the page interfaces were safe (their contexts are any). All now carry the type they read:

    class PostPolicy implements IPolicy<IncomingHttpEvent> {
      authorize(event: IncomingHttpEvent): boolean {
        return event.getUser<Actor>() !== undefined;
      }
    }

    A type-level check runs with the authz tests, and removing the parameter now fails the package build.

    SJ-30. The API explorer printed the path the spec route was declared with, so behind a router prefix the page asked for /openapi.json and got a 404, while writing the prefix into specPath made the router apply its own on top (/v1/v1/openapi.json). The explorer asks the router for the URL of the named route now. swaggerUi.specUrl states it outright for a document hosted elsewhere.

    A health probe, in @stone-js/telemetry. Telemetry is what you read after the fact; a probe is the question asked in the moment by something that cannot read. Enabling telemetry publishes /health: 200 to route traffic here, 503 to stop, and a body naming which dependency said no. Checks are declared like anything else, and resolved through the container so a check can hold the client it is checking:

    @HealthCheck("database")
    export class DatabaseCheck {
      constructor({ db }) {
        this.db = db;
      }
      async check() {
        return await this.db.ping();
      }
    }

... (truncated)

Commits

Updates @stone-js/filesystem from 0.1.2 to 0.8.16

Changelog

Sourced from @​stone-js/filesystem's changelog.

0.8.16

Patch Changes

  • @​stone-js/core@​0.8.16

0.8.15

Patch Changes

  • @​stone-js/core@​0.8.15

0.8.14

Patch Changes

  • Updated dependencies [ed1bdb8]
  • Updated dependencies [a67a77b]
    • @​stone-js/core@​0.8.14

0.8.13

Patch Changes

  • @​stone-js/core@​0.8.13

0.8.12

Patch Changes

  • Updated dependencies [c971168]
    • @​stone-js/core@​0.8.12

0.8.11

Patch Changes

  • Updated dependencies [13cebd1]
    • @​stone-js/core@​0.8.11

0.8.10

Patch Changes

  • Updated dependencies [9f074f8]
    • @​stone-js/core@​0.8.10

0.8.9

Patch Changes

... (truncated)

Commits

Updates @stone-js/node-cli-adapter from 0.2.1 to 0.8.16

Changelog

Sourced from @​stone-js/node-cli-adapter's changelog.

0.8.16

Patch Changes

  • @​stone-js/core@​0.8.16
  • @​stone-js/config@​0.8.16

0.8.15

Patch Changes

  • @​stone-js/core@​0.8.15
  • @​stone-js/config@​0.8.15

0.8.14

Patch Changes

  • ed1bdb8: fix: an extension point can say which event it reads, and telemetry answers the probe

    SJ-44, and its family. IPolicy.authorize was a function-typed property with no type parameter, so narrowing it in an implementation was rejected (TS2416) and an application had to drop its implements clause. Swept every interface an application implements: IPolicy and IAuthorizer were exposed, ICommandHandler.match ignored the event type its own interface already carried, and the page interfaces were safe (their contexts are any). All now carry the type they read:

    class PostPolicy implements IPolicy<IncomingHttpEvent> {
      authorize(event: IncomingHttpEvent): boolean {
        return event.getUser<Actor>() !== undefined;
      }
    }

    A type-level check runs with the authz tests, and removing the parameter now fails the package build.

    SJ-30. The API explorer printed the path the spec route was declared with, so behind a router prefix the page asked for /openapi.json and got a 404, while writing the prefix into specPath made the router apply its own on top (/v1/v1/openapi.json). The explorer asks the router for the URL of the named route now. swaggerUi.specUrl states it outright for a document hosted elsewhere.

    A health probe, in @stone-js/telemetry. Telemetry is what you read after the fact; a probe is the question asked in the moment by something that cannot read. Enabling telemetry publishes /health: 200 to route traffic here, 503 to stop, and a body naming which dependency said no. Checks are declared like anything else, and resolved through the container so a check can hold the client it is checking:

    @HealthCheck("database")
    export class DatabaseCheck {
      constructor({ db }) {
        this.db = db;
      }
      async check() {
        return await this.db.ping();
      }
    }

    It never hangs (a check that misses its timeout is a failed check) and never stops at the first failure. stone.telemetry.health.path moves it, false serves nothing.

... (truncated)

Commits

Updates @stone-js/pipeline from 0.1.3 to 0.8.16

Changelog

Sourced from @​stone-js/pipeline's changelog.

0.8.16

0.8.15

0.8.14

0.8.13

0.8.12

0.8.11

0.8.10

0.8.9

Patch Changes

  • 0629318: Point every README link at somewhere that exists.

    The per-module repositories were retired when the framework moved to a single one, so 36 links across 18 READMEs answered with a 404: the exact links a newcomer clicks first, "Contributing" and "API". The contributing guide now points at the monorepo, and the API reference at the published one.

    docs/ was never a durable target either, retired repository or not: it is TypeDoc output, and every build begins by deleting it.

  • f6d9fe4: fix(build): published declarations carry explicit .js extensions

    Our sources are bundler-style (extensionless relative imports) and tsc reproduces what they wrote. In a published ESM package with an exports map, a consumer on moduleResolution: nodenext cannot resolve those specifiers, so the types of everything they re-export become invisible. The reported symptom was misleading: error TS2305: Module '"@stone-js/use-react"' has no exported member 'useContainer', which reads as "the hook does not exist" rather than "the module was not resolved". A pilot project hit it on @stone-js/use-react and worked around it with moduleResolution: "bundler", which is right for bundled code but wrong for a pure Node ESM consumer.

    The shared build now rewrites relative specifiers in every emitted declaration (<file>.js, or <dir>/index.js for a directory), and the generated barrel emits them the same way. @stone-js/use-view, which carries its own rollup config, was wired to the same plugin.

    Verified across 635 declaration files: zero extensionless relative imports, and a moduleResolution: nodenext consumer importing useContainer / useBlueprint typechecks clean where it previously reported 138 errors. A pnpm run check:dts guard runs in CI right after the build so this cannot regress, including for a package that grows its own build config.

0.8.8

0.8.7

0.8.6

0.8.5

0.8.4

0.8.3

0.8.2

... (truncated)

Commits

Updates @stone-js/router from 0.2.2 to 0.8.16

Changelog

Sourced from @​stone-js/router's changelog.

0.8.16

Patch Changes

  • 7b78b7a: feat: a group's policy holds for every child, and authz composes

    A policy on a group used to be replaced by the child's own, silently: the router's default merge is child-wins, which is right for most module props (a child's contract is its contract) and wrong for a gate. Now:

    @EventHandler("/", { authz: "policy.parent" })
    export class AdminController {
      @Get("/name", { authz: "platform.operate" })
      name() {} // enforced: policy.parent, then platform.operate
    }

    Both gates hold, parent first, because the group encloses its routes, the same order group middleware runs in. authz also accepts an array outright (authz: ['a', 'b']), so a route composes its own chain: a conjunction where the first denial answers, names itself, and later gates never run, since a child policy has no business running for a caller the group already refused.

    The router learned this without learning authz: a module declares its own prop composable through its blueprint (stone.router.composableProps), and the router flattens parent and child values in order for the declared keys only. Everything undeclared keeps child-wins, unchanged.

  • 324b985: feat(router): read a route parameter from any layer, in one call

    A kernel or group middleware runs before routing, so reading a parameter took a three-line dance everywhere: find the route, bind it, read it. Even on the router layer, parameters are only bound after the route middleware have run. The router does the dance itself now:

    // A group middleware guarding /orgs/:orgCode, before any routing has happened:
    const orgCode = await router.findParam(event, "orgCode", "");
    // Or the bound route itself, for reading several things:
    const route = await router.getBoundRoute(event);

    Three properties make it safe to call from anywhere. It is a peek, not a dispatch: nothing is emitted, currentRoute is untouched, and the router's own resolution later proceeds as if nobody had looked. The match is remembered per event, so a guard reading orgCode and a locale middleware reading lang pay for one match, not two. And findParam answers the fallback when no route matches, because deciding that a request is a 404 is the router's job at dispatch, not the caller's at peek (getBoundRoute throws, since asking for a route that does not exist is a different question).

    Named in the find* family on purpose: findParam takes an event and may match, where the existing getParam reads the already-dispatched current route.

    @stone-js/i18n dogfoods it: the locale middleware asks the router the one question when the router offers it, and keeps the old dance for older routers.

  • 6d3a36e: fix: the probe escapes the API version, and a generated URL is the canonical address

    Three pilot findings, each measured before it was touched.

    • The health probe was served under the router's global prefix (/v1/health), and /health answered 404, where a load balancer actually looks. A probe is asked by a platform that knows no API version, and a probe that moves the day the API version does is a probe that goes dark. Routes can now say their relation to the global prefix, prefix: string | false on the definition (unset inherits, false escapes, a string replaces, per-route wins like strict), and both operational endpoints declare prefix: false. Measured on a real server under a /v1 router: /health 200, /v1/health 404, the API untouched under /v1.
    • route.generate() appended a trailing slash to every URL (/v1/openapi.json/): an artefact of the segment loop that this router's own matching tolerates, but that a CDN, a cache or a strict gateway may treat as a different resource. Generated URLs are the canonical declared path now, root excepted.
    • makeIncomingHttpEvent moved to @stone-js/testing/http without its documentation following: the createTestApp example now states both imports, and says why makeIncomingEvent from the main entry is not a substitute (it builds the generic event, with no URL and no HTTP methods).
    • @​stone-js/core@​0.8.16
    • @​stone-js/pipeline@​0.8.16

0.8.15

... (truncated)

Commits

Updates @stone-js/use-react from 0.3.1 to 0.8.16

Changelog

Sourced from @​stone-js/use-react's changelog.

0.8.16

Patch Changes

  • Updated dependencies [7b78b7a]
  • Updated dependencies [2c11b54]
  • Updated dependencies [324b985]
  • Updated dependencies [6d3a36e]
    • @​stone-js/router@​0.8.16
    • @​stone-js/http-core@​0.8.16
    • @​stone-js/cli@​0.8.16
    • @​stone-js/use-react-core@​0.8.16
    • @​stone-js/use-view@​0.8.16
    • @​stone-js/core@​0.8.16
    • @​stone-js/pipeline@​0.8.16
    • @​stone-js/config@​0.8.16
    • @​stone-js/filesystem@​0.8.16
    • @​stone-js/browser-core@​0.8.16
    • @​stone-js/browser-adapter@​0.8.16
    • @​stone-js/node-cli-adapter@​0.8.16

0.8.15

Patch Changes

  • @​stone-js/core@​0.8.15
  • @​stone-js/pipeline@​0.8.15
  • @​stone-js/config@​0.8.15
  • @​stone-js/filesystem@​0.8.15
  • @​stone-js/http-core@​0.8.15
  • @​stone-js/router@​0.8.15
  • @​stone-js/browser-core@​0.8.15
  • @​stone-js/browser-adapter@​0.8.15
  • @​stone-js/node-cli-adapter@​0.8.15
  • @​stone-js/use-view@​0.8.15
  • @​stone-js/use-react-core@​0.8.15
  • @​stone-js/cli@​0.8.15

0.8.14

Patch Changes

  • Updated dependencies [ed1bdb8]
  • Updated dependencies [a67a77b]
  • Updated dependencies [13915d4]
  • Updated dependencies [311d395]
    • @​stone-js/router@​0.8.14
    • @​stone-js/node-cli-adapter@​0.8.14
    • @​stone-js/core@​0.8.14
    • @​stone-js/http-core@​0.8.14

... (truncated)

Commits

Updates browserslist from 4.28.2 to 4.28.8

Release notes

Sourced from browserslist's releases.

4.28.8

  • Fixed including kaios in baseline queries (by @​Jaybhade).

4.28.7

4.28.6

4.28.5

4.28.4

  • Fixed SyntaxError regression of 4.28.3.

4.28.3

  • Fixed baseline query case-insensitivity (by @​swwind).
Changelog

Sourced from browserslist's changelog.

4.28.8

  • Fixed including kaios in baseline queries (by @​Jaybhade).

4.28.7

4.28.6

4.28.5

4.28.4

  • Fixed SyntaxError regression of 4.28.3.

4.28.3

  • Fixed baseline query case-insensitivity (by @​swwind).
Commits
  • f2f2e6c Release 4.28.8 version
  • d0787c8 Update dependencies
  • fcf8fa9 Merge pull request #939 from Jaybhade/fix/baseline-kaios-without-downstream
  • 57ecd64 fix: support "including kaios" without downstream
  • 093a0f6 Update EM banner
  • b637868 Release 4.28.7 version
  • 313f465 Update dependencies
  • c935c5a Fix regexp performance
  • d7e9e65 Rewrite structure parsing to make it always fast
  • ec4a55e Fix import order
  • Additional commits viewable in compare view
Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for browserslist since your current version.


Updates fs-extra from 11.3.5 to 11.4.0

Changelog

Sourced from fs-extra's changelog.

11.4.0 / 2026-07-23

  • Proper EEXIST error when trying to create a symlink and the dest already exists as a broken symlink (#925, #1076)

11.3.6 / 2026-06-29

  • Fix handling of symlinked destination ancestors in copy/move methods (#1071, #1073)
  • Docs typo fixed (#1074)
Commits

Updates rollup from 4.61.1 to 4.63.0

Release notes

Sourced from rollup's releases.

v4.63.0

4.63.0

2026-08-25

Features

  • Allow to analyze function return values in many more cases (#6065)

Pull Requests

v4.62.5

4.62.5

2026-08-20

Bug Fixes

  • Resolve an issue where compact mode could result in invalid module concatenations (#6468)

Pull Requests

v4.62.4

4.62.4

2026-08-01

Bug Fixes

  • Resolve a regression when using Rollup on older Linux distributions (#6467)

Pull Requests

... (truncated)

Changelog

Sourced from rollup's changelog.

4.63.0

2026-08-25

Features

  • Allow to analyze function return values in many more cases (#6065)

Pull Requests

4.62.5

2026-08-20

Bug Fixes

  • Resolve an issue where compact mode could result in invalid module concatenations (#6468)

Pull Requests

4.62.4

2026-08-01

Bug Fixes

  • Resolve a regression when using Rollup on older Linux distributions (#6467)

Pull Requests

... (truncated)

Commits

Updates rollup-plugin-dts from 6.4.1 to 6.5.1

Changelog

Sourced from rollup-plugin-dts's changelog.

6.5.1

Fixes:

  • Revert magic-string upgrade to restore cjs compatibility

6.5.0

Compatibility Notice:

This release adds compatibility with TypeScript versions 6 and 7.

Fixes:

  • Fixes to export type handling
  • Fixes to declare module handling
  • Improve shared chunks imports
  • Support literal export specifiers

Thank you:

Features, fixes and improvements in this release have been contributed by:

Commits
  • 6800c18 6.5.1
  • 99a668c Revert "Update magic-string and mess with types yet again"
  • 6ed3804 6.5.0
  • 472d04b Add changelog for new release
  • 108f6ef Update magic-string and mess with types yet again
  • ca521da Update code-frame dependency
  • 9073331 ci: renovate CI workflow
  • 42e788c docs: document declare module rewrite scope and alias limitation
  • 2178890 fix: prevent corrupted output when type-only fixes precede declare module
  • 9717329 fix: skip declare module rewrite when augmented names are renamed
  • Additional commits viewable in compare view

Updates typedoc from 0.28.19 to 0.28.20

Release notes

Sourced from typedoc's releases.

v0.28.20

Features

  • Group/category section headings (<h2>) in the default theme now include an id attribute so they can be linked to via fragment identifiers (e.g. modules.html#classes), #3029.
  • Added a @reexport modifier tag to have TypeDoc convert variable/type references as a re-export instead of a new symbol, #3096.
  • API: Introduced generateOutputsBegin and generateOutputsEnd events on Application for plugin use.

Bug Fixes

  • When --emit none is used, TypeDoc will now report warnings about missing relative paths previously reported when rendering, #3078.
  • Improved performance via asynchronously performing git and file write operations, more performant JSX rendering, and source code bundling, #3103.
  • A @hidden tag on a constructor parameter-property will now only hide the property, not both the property and the parameter, #3111.
  • Custom @group and @category titles with the same sort weight are now ordered consistently with the alphabetical reflection sort, #3120.

Thanks!

Changelog

Sourced from typedoc's changelog.

v0.28.20 (2026-07-05)

Features

  • Group/category section headings (<h2>) in the default theme now include an id attribute so they can be linked to via fragment identifiers (e.g. modules.html#classes), #3029.
  • Added a @reexport modifier tag to have TypeDoc convert variable/type references as a re-export instead of a new symbol, #3096.
  • API: Introduced generateOutputsBegin and generateOutputsEnd events on Application for plugin use.

Bug Fixes

  • When --emit none is used, TypeDoc will now report warnings about missing relative paths previously reported when rendering, #3078.
  • Improved performance via asynchronously performing git and file write operations, more performant JSX rendering, and source code bundling, #3103.
  • A @hidden tag on a constructor parameter-property will now only hide the property, not both the property and the parameter, #3111.
  • Custom @group and @category titles with the same sort weight are now ordered consistently with the alphabetical reflection sort, #3120.

Thanks!

Commits
  • 34d843b Update changelog for release
  • fbd4a25 Bump version to 0.28.20
  • 93ba157 Update dependencies in example
  • e8c5df8 Remove unnecessary files from distribution
  • 392b0dd Update dependencies
  • 8510dd4 Add missing entries in changelog before release
  • 51dc052 Update change log for 0.28.20 release
  • 72f20cd Merge branch 'fix-locale-sort-group-category-titles' into dev
  • 623f2c0 Fix failing test, accept slightly slower build for now
  • c8bdf14 Minor config tweak to improve dev build time
  • Additional commits viewable in compare view

Updates typedoc-plugin-markdown from 4.12.0 to 4.13.0

Release notes

Sourced from typedoc-plugin-markdown's releases.

[email protected]

Minor Changes

  • add a parametersFormat: "none" option to completely drop the parameter list/table and its heading (#876) - thanks @​Jym77.
  • expand type parameters in signatures when expandParameters is set (#875) - thanks @​Jym77.

Patch Changes

  • fix signature parameters (#874) - thanks @​Jym77.
  • Symbol links without a declaration reference now print a warning and render as plain text instead of attempting to resolve to the nearest link (#870).
  • formatWithPrettier now resolves Prettier config against the file being written and reads .editorconfig, so path-specific settings are honoured (#881).
Changelog

Sourced from typedoc-plugin-markdown's changelog.

4.13.0 (2026-08-25)

Minor Changes

  • add a parametersFormat: "none" option to completely drop the parameter list/table and its heading (#876) - thanks @​Jym77.
  • expand type parameters in signatures when expandParameters is set (#875) - thanks @​Jym77.

Patch Changes

  • fix signature parameters (#874) - thanks @​Jym77.
  • Symbol links without a declaration reference now print a warning and render as plain text instead of attempting to resolve to the nearest link (#870).
  • formatWithPrettier now resolves Prettier config against the file being written and reads .editorconfig, so path-specific settings are honoured (#881).
Commits
  • 57302a9 Version Packages
  • e75e95d fix(core): resolve Prettier config against the file being written (#881)
  • 3b29a55 feat(core): render symbol links without declaration references as plain text
  • cd46b32 chore(core): updated changesets and fixed tests
  • 6cab553 Merge pull request #879 from Jym77/add-parameterFormat-none
  • 8c79421 Merge pull request #878 from Jym77/expand-type-parameters
  • 73077ff fix(core): revert to unticked type parameters names
  • 6f818d7 chore(core): clean up
  • b7a9067 fix(core): do not add backticks around unexpanded type parameters in page titles
  • ce6a676 Potential fix for pull request finding
  • 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

…th 13 updates

Bumps the minor-updates group with 12 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [@stone-js/config](https://github.com/stone-foundation/stone-js-framework/tree/HEAD/stone-js-config) | `0.2.0` | `0.8.16` |
| [@stone-js/core](https://github.com/stone-foundation/stone-js-framework/tree/HEAD/stone-js-core) | `0.2.1` | `0.8.16` |
| [@stone-js/filesystem](https://github.com/stone-foundation/stone-js-framework/tree/HEAD/stone-js-filesystem) | `0.1.2` | `0.8.16` |
| [@stone-js/node-cli-adapter](https://github.com/stone-foundation/stone-js-framework/tree/HEAD/stone-js-node-cli-adapter) | `0.2.1` | `0.8.16` |
| [@stone-js/pipeline](https://github.com/stone-foundation/stone-js-framework/tree/HEAD/stone-js-pipeline) | `0.1.3` | `0.8.16` |
| [@stone-js/router](https://github.com/stone-foundation/stone-js-framework/tree/HEAD/stone-js-router) | `0.2.2` | `0.8.16` |
| [@stone-js/use-react](https://github.com/stone-foundation/stone-js-framework/tree/HEAD/stone-js-use-react) | `0.3.1` | `0.8.16` |
| [fs-extra](https://github.com/jprichardson/node-fs-extra) | `11.3.5` | `11.4.0` |
| [rollup](https://github.com/rollup/rollup) | `4.61.1` | `4.63.0` |
| [rollup-plugin-dts](https://github.com/Swatinem/rollup-plugin-dts) | `6.4.1` | `6.5.1` |
| [typedoc](https://github.com/TypeStrong/TypeDoc) | `0.28.19` | `0.28.20` |
| [typedoc-plugin-markdown](https://github.com/typedoc2md/typedoc-plugin-markdown/tree/HEAD/packages/typedoc-plugin-markdown) | `4.12.0` | `4.13.0` |



Updates `@stone-js/config` from 0.2.0 to 0.8.16
- [Release notes](https://github.com/stone-foundation/stone-js-framework/releases)
- [Changelog](https://github.com/stone-foundation/stone-js-framework/blob/main/stone-js-config/CHANGELOG.md)
- [Commits](https://github.com/stone-foundation/stone-js-framework/commits/@stone-js/[email protected]/stone-js-config)

Updates `@stone-js/core` from 0.2.1 to 0.8.16
- [Release notes](https://github.com/stone-foundation/stone-js-framework/releases)
- [Changelog](https://github.com/stone-foundation/stone-js-framework/blob/main/stone-js-core/CHANGELOG.md)
- [Commits](https://github.com/stone-foundation/stone-js-framework/commits/@stone-js/[email protected]/stone-js-core)

Updates `@stone-js/filesystem` from 0.1.2 to 0.8.16
- [Release notes](https://github.com/stone-foundation/stone-js-framework/releases)
- [Changelog](https://github.com/stone-foundation/stone-js-framework/blob/main/stone-js-filesystem/CHANGELOG.md)
- [Commits](https://github.com/stone-foundation/stone-js-framework/commits/@stone-js/[email protected]/stone-js-filesystem)

Updates `@stone-js/node-cli-adapter` from 0.2.1 to 0.8.16
- [Release notes](https://github.com/stone-foundation/stone-js-framework/releases)
- [Changelog](https://github.com/stone-foundation/stone-js-framework/blob/main/stone-js-node-cli-adapter/CHANGELOG.md)
- [Commits](https://github.com/stone-foundation/stone-js-framework/commits/@stone-js/[email protected]/stone-js-node-cli-adapter)

Updates `@stone-js/pipeline` from 0.1.3 to 0.8.16
- [Release notes](https://github.com/stone-foundation/stone-js-framework/releases)
- [Changelog](https://github.com/stone-foundation/stone-js-framework/blob/main/stone-js-pipeline/CHANGELOG.md)
- [Commits](https://github.com/stone-foundation/stone-js-framework/commits/@stone-js/[email protected]/stone-js-pipeline)

Updates `@stone-js/router` from 0.2.2 to 0.8.16
- [Release notes](https://github.com/stone-foundation/stone-js-framework/releases)
- [Changelog](https://github.com/stone-foundation/stone-js-framework/blob/main/stone-js-router/CHANGELOG.md)
- [Commits](https://github.com/stone-foundation/stone-js-framework/commits/@stone-js/[email protected]/stone-js-router)

Updates `@stone-js/use-react` from 0.3.1 to 0.8.16
- [Release notes](https://github.com/stone-foundation/stone-js-framework/releases)
- [Changelog](https://github.com/stone-foundation/stone-js-framework/blob/main/stone-js-use-react/CHANGELOG.md)
- [Commits](https://github.com/stone-foundation/stone-js-framework/commits/@stone-js/[email protected]/stone-js-use-react)

Updates `browserslist` from 4.28.2 to 4.28.8
- [Release notes](https://github.com/browserslist/browserslist/releases)
- [Changelog](https://github.com/browserslist/browserslist/blob/main/CHANGELOG.md)
- [Commits](browserslist/browserslist@4.28.2...4.28.8)

Updates `fs-extra` from 11.3.5 to 11.4.0
- [Changelog](https://github.com/jprichardson/node-fs-extra/blob/master/CHANGELOG.md)
- [Commits](jprichardson/node-fs-extra@11.3.5...11.4.0)

Updates `rollup` from 4.61.1 to 4.63.0
- [Release notes](https://github.com/rollup/rollup/releases)
- [Changelog](https://github.com/rollup/rollup/blob/master/CHANGELOG.md)
- [Commits](rollup/rollup@v4.61.1...v4.63.0)

Updates `rollup-plugin-dts` from 6.4.1 to 6.5.1
- [Changelog](https://github.com/Swatinem/rollup-plugin-dts/blob/master/CHANGELOG.md)
- [Commits](Swatinem/rollup-plugin-dts@v6.4.1...v6.5.1)

Updates `typedoc` from 0.28.19 to 0.28.20
- [Release notes](https://github.com/TypeStrong/TypeDoc/releases)
- [Changelog](https://github.com/TypeStrong/typedoc/blob/master/CHANGELOG.md)
- [Commits](TypeStrong/typedoc@v0.28.19...v0.28.20)

Updates `typedoc-plugin-markdown` from 4.12.0 to 4.13.0
- [Release notes](https://github.com/typedoc2md/typedoc-plugin-markdown/releases)
- [Changelog](https://github.com/typedoc2md/typedoc-plugin-markdown/blob/main/packages/typedoc-plugin-markdown/CHANGELOG.md)
- [Commits](https://github.com/typedoc2md/typedoc-plugin-markdown/commits/[email protected]/packages/typedoc-plugin-markdown)

---
updated-dependencies:
- dependency-name: "@stone-js/config"
  dependency-version: 0.8.16
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: minor-updates
- dependency-name: "@stone-js/core"
  dependency-version: 0.8.16
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: minor-updates
- dependency-name: "@stone-js/filesystem"
  dependency-version: 0.8.16
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: minor-updates
- dependency-name: "@stone-js/node-cli-adapter"
  dependency-version: 0.8.16
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: minor-updates
- dependency-name: "@stone-js/pipeline"
  dependency-version: 0.8.16
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: minor-updates
- dependency-name: "@stone-js/router"
  dependency-version: 0.8.16
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: minor-updates
- dependency-name: "@stone-js/use-react"
  dependency-version: 0.8.16
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: minor-updates
- dependency-name: browserslist
  dependency-version: 4.28.8
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: minor-updates
- dependency-name: fs-extra
  dependency-version: 11.4.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: minor-updates
- dependency-name: rollup
  dependency-version: 4.63.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: minor-updates
- dependency-name: rollup-plugin-dts
  dependency-version: 6.5.1
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: minor-updates
- dependency-name: typedoc
  dependency-version: 0.28.20
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: minor-updates
- dependency-name: typedoc-plugin-markdown
  dependency-version: 4.13.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: minor-updates
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot @github

dependabot Bot commented on behalf of github Aug 30, 2026

Copy link
Copy Markdown
Contributor Author

Labels

The following labels could not be found: dependencies. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant