Skip to content

chore(deps): bump the npm-updates group across 1 directory with 17 updates - #336

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/samples/weather-forecast/npm-updates-7aeeda3d6f
Open

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/samples/weather-forecast/npm-updates-7aeeda3d6f

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Oct 8, 2026 •

Copy link
Copy Markdown
Contributor

Bumps the npm-updates group with 17 updates in the /samples/weather-forecast directory:

Package From To
@staffbase/widget-sdk 3.19.1 3.19.6
acorn 8.17.0 8.19.0
dayjs 1.11.21 1.11.23
@mui/system 9.2.0 9.5.0
@rjsf/core 6.6.2 6.11.0
@rjsf/mui 6.6.2 6.11.0
@rjsf/utils 6.6.2 6.11.0
@rjsf/validator-ajv8 6.6.2 6.11.0
@testing-library/dom 10.4.1 10.4.2
@testing-library/react 16.3.2 16.3.3
core-js 3.49.0 3.50.0
jest 30.4.2 30.5.2
jest-environment-jsdom 30.4.1 30.5.2
js-base64 3.9.0 3.9.4
prettier 3.9.5 3.9.10
webpack 5.108.4 5.112.0
webpack-cli 7.2.1 7.2.3

Updates @staffbase/widget-sdk from 3.19.1 to 3.19.6

Commits

Updates acorn from 8.17.0 to 8.19.0

Commits
  • 0e0ece7 Mark version 8.19.0
  • c912cf2 Disallow additional subscripts before arrow in async arrow functions
  • f180fd7 Add Unicode v18 support (#1458)
  • ab47d42 Update test case for unexpected identifier character (#1456)
  • f53ee5f Add a contributing.md file
  • 5bd50cd Compare expression end instead of identity in parseSubscripts
  • efd7a21 Delete trailing space
  • e79ec9e Adjust dubious handling of doubleProto tracking in parseMaybeAssign
  • 93e8b90 Upgrade some dependencies with known issues
  • f065b20 Upgrade github actions to get rid of warning
  • Additional commits viewable in compare view

Updates dayjs from 1.11.21 to 1.11.23

Release notes

Sourced from dayjs's releases.

v1.11.23

1.11.23 (2026-08-17)

Bug Fixes

  • plugin: timezone plugin prevent RangeError for invalid Day.js values (#3180) (dad46e6)
  • plugin: timezone plugin prevent RangeError for invalid Day.js values (#3180) (#3181) (2a3785f)

v1.11.22

1.11.22 (2026-08-16)

Bug Fixes

  • plugin: timezone compute instance .tz() offset without host DST (#3174) (e27ee80), closes #3169
Changelog

Sourced from dayjs's changelog.

1.11.23 (2026-08-17)

Bug Fixes

  • plugin: timezone plugin prevent RangeError for invalid Day.js values (#3180) (dad46e6)
  • plugin: timezone plugin prevent RangeError for invalid Day.js values (#3180) (#3181) (2a3785f)

1.11.22 (2026-08-16)

Bug Fixes

  • plugin: timezone compute instance .tz() offset without host DST (#3174) (e27ee80), closes #3169
Commits
  • 4549b8d chore(release): 1.11.23 [skip ci]
  • 2a3785f fix(plugin): timezone plugin prevent RangeError for invalid Day.js values (#3...
  • dad46e6 fix(plugin): timezone plugin prevent RangeError for invalid Day.js values (#3...
  • ae3a550 chore(release): 1.11.22 [skip ci]
  • accfc67 D2M (#3177)
  • e27ee80 fix(plugin): timezone compute instance .tz() offset without host DST (#3174)
  • 98364bc chore: update doc
  • f6a1556 chore: update doc
  • 6609c5e chore: update doc
  • See full diff in compare view

Updates @mui/system from 9.2.0 to 9.5.0

Release notes

Sourced from @​mui/system's releases.

v9.5.0

A big thanks to the 28 contributors who made this release possible. Here are some highlights ✨:

@mui/material@9.5.0

@mui/icons-material@9.5.0

@mui/system@9.5.0

... (truncated)

Changelog

Sourced from @​mui/system's changelog.

9.5.0

Oct 9, 2026

A big thanks to the 28 contributors who made this release possible. Here are some highlights ✨:

@mui/material@9.5.0

... (truncated)

Commits
  • 1c3f8b4 v9.5.0 (#49370)
  • c0f247c [code-infra] Widen @​babel/runtime range and stop emitting empty class fields ...
  • 3c00906 [code-infra] Migrate to babel 8 (@​brijeshb42) (#49216)
  • 87a998e [system] Serialize InitColorSchemeScript configuration values (#49091)
  • 1d829b8 [test] Run module augmentation tests against built declarations (#49142)
  • 690b579 [system] Resolve InitColorSchemeScript %s placeholder at build time (#49113)
  • c74a69d Bump react to 19.3.0 (#49133)
  • 77245fd [code-infra] Convert remaining @​mui/system .js+.d.ts pairs to TypeScript (par...
  • 7b1b6b1 [system] Remove duplicated filterProps mapping in getThemeValue (#48640)
  • 8b9c366 [code-infra] Run TypeScript 7 alongside the TS6 JS API (#49075)
  • Additional commits viewable in compare view

Updates @rjsf/core from 6.6.2 to 6.11.0

Release notes

Sourced from @​rjsf/core's releases.

6.11.0

New feature

@​rjsf/core

  • Fixed a schema prop change being silently dropped when it adds a property with a default, either as the parent's reply to onChange or at any point after a change to an uncontrolled form. The guard that keeps a oneOf/anyOf option switch from reverting now only applies when the form re-derives its own formData (an uncontrolled form, or a parent holding what onChange emitted, including when it reshaped the emitted value by spreading it, storing undefined as null or round-tripping it through JSON) with the same schema and experimental_defaultFormStateBehavior, and it keeps only that formData rather than dropping the rest of the prop update, fixing #5294
  • Fixed switching between oneOf/anyOf options keeping a value the previous option's default put there, so a property whose value still matches that default, or a whole option that does, now picks up the new option's default the way a scalar property already did, and switching back to an option restores its own defaults. A property the new option cannot hold as it stands now picks the new default up as well instead of arriving empty — one whose type differs between the options, or a readOnly one edited away from its default. Values are compared whole, so a nested object the user has partly edited keeps the rest of the old option's defaults, and a value equal to the old default is replaced no matter who supplied it, including one passed in formData, since the two cannot be told apart, fixing #4476

@​rjsf/utils

  • Updated Experimental_DefaultFormStateBehavior to add a new requiredBooleanDefault option, and updated getDefaultFormState() to honor it: skip turns off the false populated for a required boolean with no default (introduced in 6.9.0 by #5170), so a form that models an unanswered boolean as its own state can keep it undefined and let required report it. The default, populateFalse, keeps the 6.9.0+ behavior

@​rjsf/validator-ata

  • Updated ata-validator from ^1.7.1 to ^1.23.0, picking up the corrected error shape for unevaluatedProperties (the error now carries params.unevaluatedProperty), the removal of a quadratic in additionalProperties: false schemas with many properties, a fix for a hang on truncated JSON input, and enforced strict-mode schema checks (#5293)

Dev / docs / playground

  • Documented the requiredBooleanDefault option in form-props.md and internals.md, and added a selector for it to the playground

6.10.1

@​rjsf/core

  • Fixed a dependencies/if branch switch nested inside an object property never sanitizing a sibling field's now-invalid value. The check gating sanitization only compared the root retrieved schema, which never reflects a conditional resolved deeper in the tree, so it always skipped sanitizing in that case, fixing (#5250)
  • Fixed NumberField losing or misinterpreting decimal input in comma-decimal locales, and passing a locale-formatted string instead of a number to custom and format-registered widgets, fixing #5199 and #5241
  • Fixed NumberField still comma-formatting the displayed value for a text widget with an explicit ui:options.inputType override in a comma-decimal locale; getInputProps() gives that override priority over the locale-based text fallback, so it rendered a native, locale-unaware <input type="number"> that rejected the comma-formatted string

@​rjsf/mantine

  • Fixed BaseInputTemplate passing an undefined value straight through to NumberInput/TextInput, which let the DOM input fall out of sync with React's controlled value and retain a stray digit after clearing a multi-digit number field (#5269)
  • Backported the fluid Container layout fix from the v7 Mantine 9 upgrade (#5260): GridTemplate's and ObjectFieldTemplate's root Container now use Mantine's fluid prop so forms fill their available width instead of centering at Mantine's default 960px max-width

@​rjsf/shadcn

  • Fixed the documented import '@rjsf/shadcn/dist/[theme].css' failing to resolve. The prebuilt stylesheets were in the published tarball but no exports entry matched them, so Node and every bundler that honours the exports map rejected the path

@​rjsf/utils

  • Fixed sanitizeDataForNewSchema() to resolve dependencies, if/then/else and allOf (not just $ref) on each property's old/new schema before comparing them, so a conditional nested inside an object property is taken into account when sanitizing its data, fixing (#5250)
  • Added schemaHasNestedConditional(), which Form uses to detect a dependencies/if nested below a schema's top level (behind a $ref, patternProperties, tuple items, additionalProperties or allOf/anyOf/oneOf) so sanitization isn't skipped just because the root retrieved schema looks unchanged (#5250)
  • Fixed getInputProps() defaulting type: number schemas to a native number input in locales whose decimal separator isn't ., where the browser rejects the localized value; it now defaults to a text input in those locales unless an explicit inputType is set
  • Added resolveDefaultWidget(), extracting the widget-name/enumOptions fallback logic shared by @rjsf/core's StringField and NumberField so the two can no longer drift out of sync
  • Upgraded @x0k/json-schema-merge to ^1.0.6, which now preserves Symbol-keyed properties (e.g. Symbol(__rjsf_ref)) when merging allOf schemas and no longer collapses distinct allOf.contains branches into one over-constrained schema; removed the corresponding Symbol-preservation and contains-extraction workarounds from retrieveSchemaInternal(), fixing (#5146)
  • Fixed defaults from a dependency subschema being omitted when getDefaultFormState() is called without form data or with an empty object, fixing #5198
  • Fixed computeDefaults() to merge a non-object schema's allOf when experimental_defaultFormStateBehavior.allOf is set to populateDefaults, so a $ref wrapped in a single-element allOf now populates the same defaults as the bare $ref does, fixing #5177

Dev / docs / playground

... (truncated)

Changelog

Sourced from @​rjsf/core's changelog.

6.11.0

@​rjsf/core

  • Fixed a schema prop change being silently dropped when it adds a property with a default, either as the parent's reply to onChange or at any point after a change to an uncontrolled form. The guard that keeps a oneOf/anyOf option switch from reverting now only applies when the form re-derives its own formData (an uncontrolled form, or a parent holding what onChange emitted, including when it reshaped the emitted value by spreading it, storing undefined as null or round-tripping it through JSON) with the same schema and experimental_defaultFormStateBehavior, and it keeps only that formData rather than dropping the rest of the prop update, fixing #5294
  • Fixed switching between oneOf/anyOf options keeping a value the previous option's default put there, so a property whose value still matches that default, or a whole option that does, now picks up the new option's default the way a scalar property already did, and switching back to an option restores its own defaults. A property the new option cannot hold as it stands now picks the new default up as well instead of arriving empty — one whose type differs between the options, or a readOnly one edited away from its default. Values are compared whole, so a nested object the user has partly edited keeps the rest of the old option's defaults, and a value equal to the old default is replaced no matter who supplied it, including one passed in formData, since the two cannot be told apart, fixing #4476

@​rjsf/utils

  • Updated Experimental_DefaultFormStateBehavior to add a new requiredBooleanDefault option, and updated getDefaultFormState() to honor it: skip turns off the false populated for a required boolean with no default (introduced in 6.9.0 by #5170), so a form that models an unanswered boolean as its own state can keep it undefined and let required report it. The default, populateFalse, keeps the 6.9.0+ behavior

@​rjsf/validator-ata

  • Updated ata-validator from ^1.7.1 to ^1.23.0, picking up the corrected error shape for unevaluatedProperties (the error now carries params.unevaluatedProperty), the removal of a quadratic in additionalProperties: false schemas with many properties, a fix for a hang on truncated JSON input, and enforced strict-mode schema checks (#5293)

Dev / docs / playground

  • Documented the requiredBooleanDefault option in form-props.md and internals.md, and added a selector for it to the playground

6.10.1

@​rjsf/core

  • Fixed a dependencies/if branch switch nested inside an object property never sanitizing a sibling field's now-invalid value. The check gating sanitization only compared the root retrieved schema, which never reflects a conditional resolved deeper in the tree, so it always skipped sanitizing in that case, fixing (#5250)
  • Fixed NumberField losing or misinterpreting decimal input in comma-decimal locales, and passing a locale-formatted string instead of a number to custom and format-registered widgets, fixing #5199 and #5241
  • Fixed NumberField still comma-formatting the displayed value for a text widget with an explicit ui:options.inputType override in a comma-decimal locale; getInputProps() gives that override priority over the locale-based text fallback, so it rendered a native, locale-unaware <input type="number"> that rejected the comma-formatted string

@​rjsf/mantine

  • Fixed BaseInputTemplate passing an undefined value straight through to NumberInput/TextInput, which let the DOM input fall out of sync with React's controlled value and retain a stray digit after clearing a multi-digit number field (#5269)
  • Backported the fluid Container layout fix from the v7 Mantine 9 upgrade (#5260): GridTemplate's and ObjectFieldTemplate's root Container now use Mantine's fluid prop so forms fill their available width instead of centering at Mantine's default 960px max-width

@​rjsf/shadcn

  • Fixed the documented import '@rjsf/shadcn/dist/[theme].css' failing to resolve. The prebuilt stylesheets were in the published tarball but no exports entry matched them, so Node and every bundler that honours the exports map rejected the path

@​rjsf/utils

  • Fixed sanitizeDataForNewSchema() to resolve dependencies, if/then/else and allOf (not just $ref) on each property's old/new schema before comparing them, so a conditional nested inside an object property is taken into account when sanitizing its data, fixing (#5250)
  • Added schemaHasNestedConditional(), which Form uses to detect a dependencies/if nested below a schema's top level (behind a $ref, patternProperties, tuple items, additionalProperties or allOf/anyOf/oneOf) so sanitization isn't skipped just because the root retrieved schema looks unchanged (#5250)
  • Fixed getInputProps() defaulting type: number schemas to a native number input in locales whose decimal separator isn't ., where the browser rejects the localized value; it now defaults to a text input in those locales unless an explicit inputType is set
  • Added resolveDefaultWidget(), extracting the widget-name/enumOptions fallback logic shared by @rjsf/core's StringField and NumberField so the two can no longer drift out of sync
  • Upgraded @x0k/json-schema-merge to ^1.0.6, which now preserves Symbol-keyed properties (e.g. Symbol(__rjsf_ref)) when merging allOf schemas and no longer collapses distinct allOf.contains branches into one over-constrained schema; removed the corresponding Symbol-preservation and contains-extraction workarounds from retrieveSchemaInternal(), fixing (#5146)
  • Fixed defaults from a dependency subschema being omitted when getDefaultFormState() is called without form data or with an empty object, fixing #5198
  • Fixed computeDefaults() to merge a non-object schema's allOf when experimental_defaultFormStateBehavior.allOf is set to populateDefaults, so a $ref wrapped in a single-element allOf now populates the same defaults as the bare $ref does, fixing #5177

Dev / docs / playground

  • Fixed the size-limit report never being posted on a pull request from a fork. The comment workflow resolved the PR from its head sha, which the base repository cannot associate with a fork's commit, so it warned and skipped — leaving a green check and no comment. The measuring job now records the PR number in its artifact, and the comment workflow looks that PR up directly, accepts it only if its head sha matches the run's trusted workflow_run head sha, and fails loudly rather than skipping when the PR cannot be found
  • Extended the size-limit checks to cover every released package rather than just @rjsf/core, @rjsf/utils and @rjsf/validator-ajv8. The checks are derived from each package's own package.json, so a new package or a dependency change needs no config edit; only the packages that already had budgets enforce one, the rest are measured and reported

... (truncated)

Commits
  • 4aeb5fa Releasing 6.11.0
  • ec97e49 Fix 4476: restore an option's defaults when switching oneOf/anyOf (#5335)
  • b1e39dc feat(utils): add requiredBooleanDefault option to opt out of the required-boo...
  • 4d1cb92 Fix #5294: apply schema changes that add a defaulted property after onChange ...
  • 3002e47 chore(deps): bump ata-validator to ^1.23.0 in @​rjsf/validator-ata (#5293)
  • 9ee0673 Releasing 6.10.1 (#5291)
  • 2241afa fix: populate defaults for a $ref wrapped in a single-element allOf (#5235)
  • 986d7c2 fix(utils): populate dependency defaults without form data (#5245)
  • 9127f50 fix(shadcn): export the prebuilt theme stylesheets so they can be imported (#...
  • 314e6f5 fix(utils): upgrade @​x0k/json-schema-merge to 1.0.6 (#5288)
  • Additional commits viewable in compare view

Updates @rjsf/mui from 6.6.2 to 6.11.0

Release notes

Sourced from @​rjsf/mui's releases.

6.11.0

New feature

@​rjsf/core

  • Fixed a schema prop change being silently dropped when it adds a property with a default, either as the parent's reply to onChange or at any point after a change to an uncontrolled form. The guard that keeps a oneOf/anyOf option switch from reverting now only applies when the form re-derives its own formData (an uncontrolled form, or a parent holding what onChange emitted, including when it reshaped the emitted value by spreading it, storing undefined as null or round-tripping it through JSON) with the same schema and experimental_defaultFormStateBehavior, and it keeps only that formData rather than dropping the rest of the prop update, fixing #5294
  • Fixed switching between oneOf/anyOf options keeping a value the previous option's default put there, so a property whose value still matches that default, or a whole option that does, now picks up the new option's default the way a scalar property already did, and switching back to an option restores its own defaults. A property the new option cannot hold as it stands now picks the new default up as well instead of arriving empty — one whose type differs between the options, or a readOnly one edited away from its default. Values are compared whole, so a nested object the user has partly edited keeps the rest of the old option's defaults, and a value equal to the old default is replaced no matter who supplied it, including one passed in formData, since the two cannot be told apart, fixing #4476

@​rjsf/utils

  • Updated Experimental_DefaultFormStateBehavior to add a new requiredBooleanDefault option, and updated getDefaultFormState() to honor it: skip turns off the false populated for a required boolean with no default (introduced in 6.9.0 by #5170), so a form that models an unanswered boolean as its own state can keep it undefined and let required report it. The default, populateFalse, keeps the 6.9.0+ behavior

@​rjsf/validator-ata

  • Updated ata-validator from ^1.7.1 to ^1.23.0, picking up the corrected error shape for unevaluatedProperties (the error now carries params.unevaluatedProperty), the removal of a quadratic in additionalProperties: false schemas with many properties, a fix for a hang on truncated JSON input, and enforced strict-mode schema checks (#5293)

Dev / docs / playground

  • Documented the requiredBooleanDefault option in form-props.md and internals.md, and added a selector for it to the playground

6.10.1

@​rjsf/core

  • Fixed a dependencies/if branch switch nested inside an object property never sanitizing a sibling field's now-invalid value. The check gating sanitization only compared the root retrieved schema, which never reflects a conditional resolved deeper in the tree, so it always skipped sanitizing in that case, fixing (#5250)
  • Fixed NumberField losing or misinterpreting decimal input in comma-decimal locales, and passing a locale-formatted string instead of a number to custom and format-registered widgets, fixing #5199 and #5241
  • Fixed NumberField still comma-formatting the displayed value for a text widget with an explicit ui:options.inputType override in a comma-decimal locale; getInputProps() gives that override priority over the locale-based text fallback, so it rendered a native, locale-unaware <input type="number"> that rejected the comma-formatted string

@​rjsf/mantine

  • Fixed BaseInputTemplate passing an undefined value straight through to NumberInput/TextInput, which let the DOM input fall out of sync with React's controlled value and retain a stray digit after clearing a multi-digit number field (#5269)
  • Backported the fluid Container layout fix from the v7 Mantine 9 upgrade (#5260): GridTemplate's and ObjectFieldTemplate's root Container now use Mantine's fluid prop so forms fill their available width instead of centering at Mantine's default 960px max-width

@​rjsf/shadcn

  • Fixed the documented import '@rjsf/shadcn/dist/[theme].css' failing to resolve. The prebuilt stylesheets were in the published tarball but no exports entry matched them, so Node and every bundler that honours the exports map rejected the path

@​rjsf/utils

  • Fixed sanitizeDataForNewSchema() to resolve dependencies, if/then/else and allOf (not just $ref) on each property's old/new schema before comparing them, so a conditional nested inside an object property is taken into account when sanitizing its data, fixing (#5250)
  • Added schemaHasNestedConditional(), which Form uses to detect a dependencies/if nested below a schema's top level (behind a $ref, patternProperties, tuple items, additionalProperties or allOf/anyOf/oneOf) so sanitization isn't skipped just because the root retrieved schema looks unchanged (#5250)
  • Fixed getInputProps() defaulting type: number schemas to a native number input in locales whose decimal separator isn't ., where the browser rejects the localized value; it now defaults to a text input in those locales unless an explicit inputType is set
  • Added resolveDefaultWidget(), extracting the widget-name/enumOptions fallback logic shared by @rjsf/core's StringField and NumberField so the two can no longer drift out of sync
  • Upgraded @x0k/json-schema-merge to ^1.0.6, which now preserves Symbol-keyed properties (e.g. Symbol(__rjsf_ref)) when merging allOf schemas and no longer collapses distinct allOf.contains branches into one over-constrained schema; removed the corresponding Symbol-preservation and contains-extraction workarounds from retrieveSchemaInternal(), fixing (#5146)
  • Fixed defaults from a dependency subschema being omitted when getDefaultFormState() is called without form data or with an empty object, fixing #5198
  • Fixed computeDefaults() to merge a non-object schema's allOf when experimental_defaultFormStateBehavior.allOf is set to populateDefaults, so a $ref wrapped in a single-element allOf now populates the same defaults as the bare $ref does, fixing #5177

Dev / docs / playground

... (truncated)

Changelog

Sourced from @​rjsf/mui's changelog.

6.11.0

@​rjsf/core

  • Fixed a schema prop change being silently dropped when it adds a property with a default, either as the parent's reply to onChange or at any point after a change to an uncontrolled form. The guard that keeps a oneOf/anyOf option switch from reverting now only applies when the form re-derives its own formData (an uncontrolled form, or a parent holding what onChange emitted, including when it reshaped the emitted value by spreading it, storing undefined as null or round-tripping it through JSON) with the same schema and experimental_defaultFormStateBehavior, and it keeps only that formData rather than dropping the rest of the prop update, fixing #5294
  • Fixed switching between oneOf/anyOf options keeping a value the previous option's default put there, so a property whose value still matches that default, or a whole option that does, now picks up the new option's default the way a scalar property already did, and switching back to an option restores its own defaults. A property the new option cannot hold as it stands now picks the new default up as well instead of arriving empty — one whose type differs between the options, or a readOnly one edited away from its default. Values are compared ...

    Description has been truncated

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code minor Pull requests with new features labels Oct 8, 2026
@dependabot
dependabot Bot requested a review from a team as a code owner October 8, 2026 15:06
@dependabot
dependabot Bot requested a review from geodomou781 October 8, 2026 15:06
@dependabot dependabot Bot added the dependencies Pull requests that update a dependency file label Oct 8, 2026
@dependabot
dependabot Bot requested a review from robertvangor October 8, 2026 15:06
@dependabot dependabot Bot added javascript Pull requests that update Javascript code minor Pull requests with new features labels Oct 8, 2026
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/samples/weather-forecast/npm-updates-7aeeda3d6f branch 2 times, most recently from 1b57592 to fd572fe Compare October 13, 2026 11:00
…dates

Bumps the npm-updates group with 17 updates in the /samples/weather-forecast directory:

| Package | From | To |
| --- | --- | --- |
| [@staffbase/widget-sdk](https://github.com/Staffbase/widget-sdk) | `3.19.1` | `3.19.6` |
| [acorn](https://github.com/acornjs/acorn) | `8.17.0` | `8.19.0` |
| [dayjs](https://github.com/iamkun/dayjs) | `1.11.21` | `1.11.23` |
| [@mui/system](https://github.com/mui/material-ui/tree/HEAD/packages/mui-system) | `9.2.0` | `9.5.0` |
| [@rjsf/core](https://github.com/rjsf-team/react-jsonschema-form) | `6.6.2` | `6.11.0` |
| [@rjsf/mui](https://github.com/rjsf-team/react-jsonschema-form) | `6.6.2` | `6.11.0` |
| [@rjsf/utils](https://github.com/rjsf-team/react-jsonschema-form) | `6.6.2` | `6.11.0` |
| [@rjsf/validator-ajv8](https://github.com/rjsf-team/react-jsonschema-form) | `6.6.2` | `6.11.0` |
| [@testing-library/dom](https://github.com/testing-library/dom-testing-library) | `10.4.1` | `10.4.2` |
| [@testing-library/react](https://github.com/testing-library/react-testing-library) | `16.3.2` | `16.3.3` |
| [core-js](https://github.com/zloirock/core-js/tree/HEAD/packages/core-js) | `3.49.0` | `3.50.0` |
| [jest](https://github.com/jestjs/jest/tree/HEAD/packages/jest) | `30.4.2` | `30.5.2` |
| [jest-environment-jsdom](https://github.com/jestjs/jest/tree/HEAD/packages/jest-environment-jsdom) | `30.4.1` | `30.5.2` |
| [js-base64](https://github.com/dankogai/js-base64) | `3.9.0` | `3.9.4` |
| [prettier](https://github.com/prettier/prettier) | `3.9.5` | `3.9.10` |
| [webpack](https://github.com/webpack/webpack) | `5.108.4` | `5.112.0` |
| [webpack-cli](https://github.com/webpack/webpack-cli) | `7.2.1` | `7.2.3` |



Updates `@staffbase/widget-sdk` from 3.19.1 to 3.19.6
- [Commits](https://github.com/Staffbase/widget-sdk/commits)

Updates `acorn` from 8.17.0 to 8.19.0
- [Commits](acornjs/acorn@8.17.0...8.19.0)

Updates `dayjs` from 1.11.21 to 1.11.23
- [Release notes](https://github.com/iamkun/dayjs/releases)
- [Changelog](https://github.com/iamkun/dayjs/blob/v1.11.23/CHANGELOG.md)
- [Commits](iamkun/dayjs@v1.11.21...v1.11.23)

Updates `@mui/system` from 9.2.0 to 9.5.0
- [Release notes](https://github.com/mui/material-ui/releases)
- [Changelog](https://github.com/mui/material-ui/blob/v9.5.0/CHANGELOG.md)
- [Commits](https://github.com/mui/material-ui/commits/v9.5.0/packages/mui-system)

Updates `@rjsf/core` from 6.6.2 to 6.11.0
- [Release notes](https://github.com/rjsf-team/react-jsonschema-form/releases)
- [Changelog](https://github.com/rjsf-team/react-jsonschema-form/blob/main/CHANGELOG.md)
- [Commits](rjsf-team/react-jsonschema-form@6.6.2...v6.11.0)

Updates `@rjsf/mui` from 6.6.2 to 6.11.0
- [Release notes](https://github.com/rjsf-team/react-jsonschema-form/releases)
- [Changelog](https://github.com/rjsf-team/react-jsonschema-form/blob/main/CHANGELOG.md)
- [Commits](rjsf-team/react-jsonschema-form@6.6.2...v6.11.0)

Updates `@rjsf/utils` from 6.6.2 to 6.11.0
- [Release notes](https://github.com/rjsf-team/react-jsonschema-form/releases)
- [Changelog](https://github.com/rjsf-team/react-jsonschema-form/blob/main/CHANGELOG.md)
- [Commits](rjsf-team/react-jsonschema-form@6.6.2...v6.11.0)

Updates `@rjsf/validator-ajv8` from 6.6.2 to 6.11.0
- [Release notes](https://github.com/rjsf-team/react-jsonschema-form/releases)
- [Changelog](https://github.com/rjsf-team/react-jsonschema-form/blob/main/CHANGELOG.md)
- [Commits](rjsf-team/react-jsonschema-form@6.6.2...v6.11.0)

Updates `@testing-library/dom` from 10.4.1 to 10.4.2
- [Release notes](https://github.com/testing-library/dom-testing-library/releases)
- [Changelog](https://github.com/testing-library/dom-testing-library/blob/main/CHANGELOG.md)
- [Commits](testing-library/dom-testing-library@v10.4.1...v10.4.2)

Updates `@testing-library/react` from 16.3.2 to 16.3.3
- [Release notes](https://github.com/testing-library/react-testing-library/releases)
- [Changelog](https://github.com/testing-library/react-testing-library/blob/main/CHANGELOG.md)
- [Commits](testing-library/react-testing-library@v16.3.2...v16.3.3)

Updates `core-js` from 3.49.0 to 3.50.0
- [Release notes](https://github.com/zloirock/core-js/releases)
- [Changelog](https://github.com/zloirock/core-js/blob/master/CHANGELOG.md)
- [Commits](https://github.com/zloirock/core-js/commits/v3.50.0/packages/core-js)

Updates `jest` from 30.4.2 to 30.5.2
- [Release notes](https://github.com/jestjs/jest/releases)
- [Changelog](https://github.com/jestjs/jest/blob/main/CHANGELOG.md)
- [Commits](https://github.com/jestjs/jest/commits/v30.5.2/packages/jest)

Updates `jest-environment-jsdom` from 30.4.1 to 30.5.2
- [Release notes](https://github.com/jestjs/jest/releases)
- [Changelog](https://github.com/jestjs/jest/blob/main/CHANGELOG.md)
- [Commits](https://github.com/jestjs/jest/commits/v30.5.2/packages/jest-environment-jsdom)

Updates `js-base64` from 3.9.0 to 3.9.4
- [Commits](dankogai/js-base64@3.9.0...v3.9.4)

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

Updates `webpack` from 5.108.4 to 5.112.0
- [Release notes](https://github.com/webpack/webpack/releases)
- [Changelog](https://github.com/webpack/webpack/blob/main/CHANGELOG.md)
- [Commits](webpack/webpack@v5.108.4...v5.112.0)

Updates `webpack-cli` from 7.2.1 to 7.2.3
- [Release notes](https://github.com/webpack/webpack-cli/releases)
- [Changelog](https://github.com/webpack/webpack-cli/blob/main/CHANGELOG.md)
- [Commits](https://github.com/webpack/webpack-cli/compare/webpack-cli@7.2.1...webpack-cli@7.2.3)

---
updated-dependencies:
- dependency-name: "@mui/system"
  dependency-version: 9.4.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: npm-updates
- dependency-name: "@rjsf/core"
  dependency-version: 6.11.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: npm-updates
- dependency-name: "@rjsf/mui"
  dependency-version: 6.11.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: npm-updates
- dependency-name: "@rjsf/utils"
  dependency-version: 6.11.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: npm-updates
- dependency-name: "@rjsf/validator-ajv8"
  dependency-version: 6.11.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: npm-updates
- dependency-name: "@staffbase/widget-sdk"
  dependency-version: 3.19.6
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: npm-updates
- dependency-name: "@testing-library/dom"
  dependency-version: 10.4.2
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: npm-updates
- dependency-name: "@testing-library/react"
  dependency-version: 16.3.3
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: npm-updates
- dependency-name: acorn
  dependency-version: 8.18.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: npm-updates
- dependency-name: core-js
  dependency-version: 3.50.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: npm-updates
- dependency-name: dayjs
  dependency-version: 1.11.23
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: npm-updates
- dependency-name: jest
  dependency-version: 30.5.2
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: npm-updates
- dependency-name: jest-environment-jsdom
  dependency-version: 30.5.2
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: npm-updates
- dependency-name: js-base64
  dependency-version: 3.9.4
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: npm-updates
- dependency-name: prettier
  dependency-version: 3.9.9
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: npm-updates
- dependency-name: webpack
  dependency-version: 5.111.1
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: npm-updates
- dependency-name: webpack-cli
  dependency-version: 7.2.3
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: npm-updates
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/samples/weather-forecast/npm-updates-7aeeda3d6f branch from fd572fe to 364f320 Compare October 26, 2026 07:07
@coderabbitai

coderabbitai Bot commented Oct 26, 2026

Copy link
Copy Markdown

Review in Change Stack →

No actionable comments were generated in the recent review.

Recent review info
Run configuration
  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: CHILL
  • Plan: Enterprise
  • Run ID: 3f8b0989-db17-4c44-909c-a3c65f95d169
Commits

Reviewing files that changed from the base of the PR and between e40586c and 364f320.

Files ignored due to path filters: 1
  • samples/weather-forecast/yarn.lock is excluded by !**/yarn.lock, !**/*.lock
Files selected for processing: 1
  • samples/weather-forecast/package.json

Included review availability: This review used your included allowance. Your plan provides up to 12 included reviews per hour; 2 remain after this review.

Summary by CodeRabbit

  • Chores
    • Updated the weather forecast sample’s supporting packages and build tools to newer versions. The sample’s build tool now uses a specific version. No changes to the sample’s visible features or behavior were reported.

Walkthrough

The weather forecast sample updates runtime and development dependency versions and pins webpack to a newer version. The changes are limited to its package manifest; the supplied diff does not show changes to a production request path.

Changes

Weather forecast dependency updates

Layer / File(s) Summary
Update sample dependency versions
samples/weather-forecast/package.json
The manifest updates runtime dependencies, UI and form packages, test and build tools, and the webpack resolution. Axios and date-fns remain unchanged.

Priority: Low

Estimated code review effort: 2 (Simple) | ~8 minutes

Merge Risk: Minimal · up to 364f3

The dependency updates are internally consistent, with no identified merge-blocking risk.

Architecture risk: Low · up to 364f3

The change affects 1 system.

Changed systems: samples

Architecture concerns
No architecture-level concerns identified.

Review details

Systems and components

  • observed — samples (service) was modified; 1 changed file maps to changed impact.

Before / after behavior

  • observed — Modified behavior in samples/weather-forecast/package.json: Updated @staffbase/widget-sdk, acorn, and dayjs version constraints; axios and date-fns remain unchanged.
  • observed — Modified behavior in samples/weather-forecast/package.json: Updated @mui/system and all four @rjsf package versions from 6.6.2 to 6.11.0, and raised @testing-library/dom and @testing-library/react patch versions. Other entries in this range are unchanged.
  • observed — Modified behavior in samples/weather-forecast/package.json: Raised versions for core-js, Jest and its jsdom environment, js-base64, Prettier, webpack, and webpack-cli; changed the webpack resolution from 5.108.4 to 5.112.0. Other entries in this range are unchanged.
Pre-merge checks: Passed 4
Check name Status Explanation
Title check Passed The title clearly describes the 17 dependency updates in one directory. The change is limited to sample dependency metadata and does not indicate a production outage path.
Description check Passed The description directly documents the dependency updates, version changes, affected directory, and release notes. It matches the changeset.
Linked Issues check Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check Passed Check skipped because no linked issues were found for this pull request.
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Comment @coderabbitai help to get the list of available commands.

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 minor Pull requests with new features

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants