dependabot[bot] opened a new pull request, #44378: URL: https://github.com/apache/superset/pull/44378
Bumps the rjsf group in /superset-frontend with 3 updates: [@rjsf/core](https://github.com/rjsf-team/react-jsonschema-form), [@rjsf/utils](https://github.com/rjsf-team/react-jsonschema-form) and [@rjsf/validator-ajv8](https://github.com/rjsf-team/react-jsonschema-form). Updates `@rjsf/core` from 6.8.0 to 6.10.0 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/rjsf-team/react-jsonschema-form/releases";>@rjsf/core's releases</a>.</em></p> <blockquote> <h2>6.10.0</h2> <h1>New Feature added</h1> <p><a href="https://rjsf-team.github.io/react-jsonschema-form/docs/api-reference/uiSchema#autocapitalize";>autocapitalize</a> support was added to the uiSchema</p> <p>Also, since 6.9.0 failed to release properly, this also contains all of its <a href="https://github.com/rjsf-team/react-jsonschema-form/releases/tag/v6.9.0";>content</a></p> <h2><code>@rjsf/chakra-ui</code></h2> <ul> <li>Removed an <code>environment</code> prop the test wrapper passed to <code>EnvironmentProvider</code>, which has no such prop and silently ignored it</li> </ul> <h2><code>@rjsf/core</code></h2> <ul> <li>Fixed defaults not being restored when returning to an <code>anyOf</code> or <code>oneOf</code> option with disjoint properties (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/3736";>#3736</a>)</li> <li>Added <code>ui:autocapitalize</code> support for inputs rendered by <code>BaseInputTemplate</code>, allowing mobile keyboards to apply the requested capitalization behavior (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/2187";>#2187</a>)</li> </ul> <h2><code>@rjsf/mantine</code></h2> <ul> <li>Added <code>ui:autocapitalize</code> support for text inputs (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/2187";>#2187</a>)</li> </ul> <h2><code>@rjsf/mui</code></h2> <ul> <li>Added <code>ui:autocapitalize</code> support for text inputs (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/2187";>#2187</a>)</li> </ul> <h2><code>@rjsf/utils</code></h2> <ul> <li>Fixed <code>sanitizeDataForNewSchema()</code> clearing existing arrays or preserving stale <code>undefined</code> values instead of retaining data or applying defaults for properties newly defined by the incoming schema (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/3736";>#3736</a>)</li> <li>Added <code>autocapitalize</code> UI option handling to <code>getInputProps()</code> and its public input prop types (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/2187";>#2187</a>)</li> </ul> <h2><code>@rjsf/validator-ajv8</code></h2> <ul> <li>Changed the <code>standaloneCode</code> import to name the file, <code>ajv/dist/standalone/index.js</code>, instead of the directory subpath <code>ajv/dist/standalone</code>. A <code>tsc-alias</code> replacer used to patch this into the emitted output; the source now says what it means. No public API changed</li> </ul> <h2>Dev / docs / playground</h2> <ul> <li>Relative TypeScript imports now name their real <code>.ts</code>/<code>.tsx</code> source file (and an explicit <code>index.ts</code> for directory imports), and TypeScript's <code>rewriteRelativeImportExtensions</code> emits the <code>.js</code> specifiers directly. This removes <code>tsc-alias</code> and its post-emit string rewriting entirely, along with the <code>tsc-alias-replacer/</code> directory, both <code>tsconfig.replacer.json</code> files, the <code>compileReplacer</code> scripts and <code>move-file-cli</code>. Naming the source file rather than the output is deliberate: Node's native type stripping requires exact <code>.ts</code> extensions and does no extension or directory-index searching, so this avoids a second repository-wide import migration later</li> <li>Fixed <code>packages/daisyui/test/tsconfig.json</code>, which was configured to emit into <code>../dist</code> — the esbuild/rollup bundle output directory — instead of type-checking without emit like every other test project</li> <li>Collapsed each package's <code>tsconfig.json</code> + <code>tsconfig.build.json</code> + <code>src/tsconfig.json</code> chain into one source config plus one test config extending a new shared root <code>tsconfig.test.json</code>. Building a package no longer pulls its dependencies' test projects into the graph</li> <li>Fixed the root <code>tsconfig.json</code>, which referenced <code>snapshot-tests</code> twice and omitted <code>mantine</code>, <code>primereact</code>, <code>validator-ata</code> and <code>validator-cfworker</code>. It now lists every source and test project once, and a new root <code>typecheck</code> script runs in CI, so tests are typechecked for the first time. That surfaced stale tests in <code>@rjsf/chakra-ui</code> and <code>@rjsf/validator-ata</code> and two drifted playground samples, fixed here. <code>@rjsf/chakra-ui</code>'s <code>type-check</code> script previously ran against a solution config with <code>files: []</code> and checked nothing</li> <li>Every package now emits <code>lib/</code> with the same settings: <code>esnext</code> target plus <code>.js.map</code> and <code>.d.ts.map</code>. Previously only <code>@rjsf/core</code> did; the rest emitted ES2018 with JS source maps only, depending on which root config their <code>src/tsconfig.json</code> extended</li> <li><code>tsconfig.tsbuildinfo</code> is no longer written into <code>lib/</code> and published with it. In 6.8.0 it was 446 kB of <code>@rjsf/antd</code>'s 959 kB unpacked tarball</li> <li>Set <code>"types": []</code> in <code>tsconfig.base.json</code> so packages no longer see every hoisted <code>@types/*</code>, with Node-using packages opting in, and <code>"lib": ["ESNext"]</code> in the three validator packages so they cannot compile against browser globals</li> <li><code>build:ts</code> is now plain <code>tsc -b</code>. The old <code>rimraf ./lib</code> also deleted the build-info, forcing a full rebuild every time; the build-info is now an Nx <code>build</code> output alongside <code>lib/</code> so cache restores stay coherent</li> <li>Added <code>"type": "module"</code> to <code>@rjsf/snapshot-tests</code>, which publishes ESM <code>.js</code> files</li> <li>Enabled <code>verbatimModuleSyntax</code>, so type-only imports must be written as <code>import type</code>. The one import it affected, <code>React</code> in <code>@rjsf/utils</code>'s <code>shouldRender.ts</code>, is now type-only, so emitted output is unchanged</li> <li>Documented <code>ui:autocapitalize</code>, added it to the simple playground sample, and added cross-theme regression coverage (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/2187";>#2187</a>)</li> </ul> <h2>6.9.0</h2> <blockquote> <p><strong>Potentially breaking change:</strong> <code>lodash</code> and <code>lodash-es</code> are no longer dependencies of any <code>@rjsf/*</code> package. No RJSF public API changed, but an application that imports <code>lodash</code> itself without declaring it — relying on it being hoisted into <code>node_modules</code> because RJSF depended on it — must now add <code>lodash</code> to its own <code>package.json</code>.</p> </blockquote> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/rjsf-team/react-jsonschema-form/blob/main/CHANGELOG.md";>@rjsf/core's changelog</a>.</em></p> <blockquote> <h1>6.10.0</h1> <h2><code>@rjsf/chakra-ui</code></h2> <ul> <li>Removed an <code>environment</code> prop the test wrapper passed to <code>EnvironmentProvider</code>, which has no such prop and silently ignored it</li> </ul> <h2><code>@rjsf/core</code></h2> <ul> <li>Fixed defaults not being restored when returning to an <code>anyOf</code> or <code>oneOf</code> option with disjoint properties (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/3736";>#3736</a>)</li> <li>Added <code>ui:autocapitalize</code> support for inputs rendered by <code>BaseInputTemplate</code>, allowing mobile keyboards to apply the requested capitalization behavior (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/2187";>#2187</a>)</li> </ul> <h2><code>@rjsf/mantine</code></h2> <ul> <li>Added <code>ui:autocapitalize</code> support for text inputs (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/2187";>#2187</a>)</li> </ul> <h2><code>@rjsf/mui</code></h2> <ul> <li>Added <code>ui:autocapitalize</code> support for text inputs (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/2187";>#2187</a>)</li> </ul> <h2><code>@rjsf/utils</code></h2> <ul> <li>Fixed <code>sanitizeDataForNewSchema()</code> clearing existing arrays or preserving stale <code>undefined</code> values instead of retaining data or applying defaults for properties newly defined by the incoming schema (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/3736";>#3736</a>)</li> <li>Added <code>autocapitalize</code> UI option handling to <code>getInputProps()</code> and its public input prop types (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/2187";>#2187</a>)</li> </ul> <h2>Dev / docs / playground</h2> <ul> <li>Documented <code>ui:autocapitalize</code>, added it to the simple playground sample, and added cross-theme regression coverage (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/2187";>#2187</a>)</li> </ul> <h2><code>@rjsf/validator-ajv8</code></h2> <ul> <li>Changed the <code>standaloneCode</code> import to name the file, <code>ajv/dist/standalone/index.js</code>, instead of the directory subpath <code>ajv/dist/standalone</code>. A <code>tsc-alias</code> replacer used to patch this into the emitted output; the source now says what it means. No public API changed</li> </ul> <h2>Dev / docs / playground</h2> <ul> <li>Relative TypeScript imports now name their real <code>.ts</code>/<code>.tsx</code> source file (and an explicit <code>index.ts</code> for directory imports), and TypeScript's <code>rewriteRelativeImportExtensions</code> emits the <code>.js</code> specifiers directly. This removes <code>tsc-alias</code> and its post-emit string rewriting entirely, along with the <code>tsc-alias-replacer/</code> directory, both <code>tsconfig.replacer.json</code> files, the <code>compileReplacer</code> scripts and <code>move-file-cli</code>. Naming the source file rather than the output is deliberate: Node's native type stripping requires exact <code>.ts</code> extensions and does no extension or directory-index searching, so this avoids a second repository-wide import migration later</li> <li>Fixed <code>packages/daisyui/test/tsconfig.json</code>, which was configured to emit into <code>../dist</code> — the esbuild/rollup bundle output directory — instead of type-checking without emit like every other test project</li> <li>Collapsed each package's <code>tsconfig.json</code> + <code>tsconfig.build.json</code> + <code>src/tsconfig.json</code> chain into one source config plus one test config extending a new shared root <code>tsconfig.test.json</code>. Building a package no longer pulls its dependencies' test projects into the graph</li> <li>Fixed the root <code>tsconfig.json</code>, which referenced <code>snapshot-tests</code> twice and omitted <code>mantine</code>, <code>primereact</code>, <code>validator-ata</code> and <code>validator-cfworker</code>. It now lists every source and test project once, and a new root <code>typecheck</code> script runs in CI, so tests are typechecked for the first time. That surfaced stale tests in <code>@rjsf/chakra-ui</code> and <code>@rjsf/validator-ata</code> and two drifted playground samples, fixed here. <code>@rjsf/chakra-ui</code>'s <code>type-check</code> script previously ran against a solution config with <code>files: []</code> and checked nothing</li> <li>Every package now emits <code>lib/</code> with the same settings: <code>esnext</code> target plus <code>.js.map</code> and <code>.d.ts.map</code>. Previously only <code>@rjsf/core</code> did; the rest emitted ES2018 with JS source maps only, depending on which root config their <code>src/tsconfig.json</code> extended</li> <li><code>tsconfig.tsbuildinfo</code> is no longer written into <code>lib/</code> and published with it. In 6.8.0 it was 446 kB of <code>@rjsf/antd</code>'s 959 kB unpacked tarball</li> <li>Set <code>"types": []</code> in <code>tsconfig.base.json</code> so packages no longer see every hoisted <code>@types/*</code>, with Node-using packages opting in, and <code>"lib": ["ESNext"]</code> in the three validator packages so they cannot compile against browser globals</li> <li><code>build:ts</code> is now plain <code>tsc -b</code>. The old <code>rimraf ./lib</code> also deleted the build-info, forcing a full rebuild every time; the build-info is now an Nx <code>build</code> output alongside <code>lib/</code> so cache restores stay coherent</li> <li>Added <code>"type": "module"</code> to <code>@rjsf/snapshot-tests</code>, which publishes ESM <code>.js</code> files</li> <li>Enabled <code>verbatimModuleSyntax</code>, so type-only imports must be written as <code>import type</code>. The one import it affected, <code>React</code> in <code>@rjsf/utils</code>'s <code>shouldRender.ts</code>, is now type-only, so emitted output is unchanged</li> </ul> <h1>6.9.0</h1> <blockquote> <p><strong>Potentially breaking change:</strong> <code>lodash</code> and <code>lodash-es</code> are no longer dependencies of any <code>@rjsf/*</code> package. No RJSF public API changed, but an application that imports <code>lodash</code> itself without declaring it — relying on it being hoisted into <code>node_modules</code> because RJSF depended on it — must now add <code>lodash</code> to its own <code>package.json</code>.</p> </blockquote> <h2><code>@rjsf/antd</code></h2> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/rjsf-team/react-jsonschema-form/commit/014f2e0ec4201e8b2f0244be49563101846f8814";><code>014f2e0</code></a> Releasing 6.10.0</li> <li><a href="https://github.com/rjsf-team/react-jsonschema-form/commit/d23f31e3dd80eb39d06183cef0c17f771b4f67cf";><code>d23f31e</code></a> Upgrade Nx and fix failing release (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/5251";>#5251</a>)</li> <li><a href="https://github.com/rjsf-team/react-jsonschema-form/commit/bc9feedd4e34fe2c3798d94b92d23d9adb44df1f";><code>bc9feed</code></a> feat: support ui:autocapitalize (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/5240";>#5240</a>)</li> <li><a href="https://github.com/rjsf-team/react-jsonschema-form/commit/1a2bb662b79dc28156a83eccfffb91fc33dac3b2";><code>1a2bb66</code></a> build: one tsconfig per package, typecheck tests in CI, stop publishing tsbui...</li> <li><a href="https://github.com/rjsf-team/react-jsonschema-form/commit/bd1775eac7833de74f3fde387aafca952b481c05";><code>bd1775e</code></a> chore(deps): bump fast-uri from 4.1.3 to 4.1.4 (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/5239";>#5239</a>)</li> <li><a href="https://github.com/rjsf-team/react-jsonschema-form/commit/e0f36c9434cc3e187e6f3d4ec9990fccac44a568";><code>e0f36c9</code></a> build: import real .ts/.tsx paths in source and drop tsc-alias (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/5233";>#5233</a>)</li> <li><a href="https://github.com/rjsf-team/react-jsonschema-form/commit/67def97b49881ebab977a7f42359f03ad02f1e76";><code>67def97</code></a> fix(utils): Use defaults when toggling between oneOf/anyOf schemas (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/5218";>#5218</a>)</li> <li><a href="https://github.com/rjsf-team/react-jsonschema-form/commit/84c424e0c76ef4417ebb45e5523987ae0140bdbc";><code>84c424e</code></a> Releasing 6.9.0 (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/5234";>#5234</a>)</li> <li><a href="https://github.com/rjsf-team/react-jsonschema-form/commit/dc056e2de677613247f015258fc46ee6263ce807";><code>dc056e2</code></a> Fixes related to empty values (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/5222";>#5222</a>) (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/5225";>#5225</a>)</li> <li><a href="https://github.com/rjsf-team/react-jsonschema-form/commit/b569fc64cfe8e68d95d6e3d1d14d8e4ec52473ba";><code>b569fc6</code></a> test: resolve workspace packages from source via an <code>@rjsf/source</code> export condi...</li> <li>Additional commits viewable in <a href="https://github.com/rjsf-team/react-jsonschema-form/compare/v6.8.0...v6.10.0";>compare view</a></li> </ul> </details> <br /> Updates `@rjsf/utils` from 6.8.0 to 6.10.0 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/rjsf-team/react-jsonschema-form/releases";>@rjsf/utils's releases</a>.</em></p> <blockquote> <h2>6.10.0</h2> <h1>New Feature added</h1> <p><a href="https://rjsf-team.github.io/react-jsonschema-form/docs/api-reference/uiSchema#autocapitalize";>autocapitalize</a> support was added to the uiSchema</p> <p>Also, since 6.9.0 failed to release properly, this also contains all of its <a href="https://github.com/rjsf-team/react-jsonschema-form/releases/tag/v6.9.0";>content</a></p> <h2><code>@rjsf/chakra-ui</code></h2> <ul> <li>Removed an <code>environment</code> prop the test wrapper passed to <code>EnvironmentProvider</code>, which has no such prop and silently ignored it</li> </ul> <h2><code>@rjsf/core</code></h2> <ul> <li>Fixed defaults not being restored when returning to an <code>anyOf</code> or <code>oneOf</code> option with disjoint properties (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/3736";>#3736</a>)</li> <li>Added <code>ui:autocapitalize</code> support for inputs rendered by <code>BaseInputTemplate</code>, allowing mobile keyboards to apply the requested capitalization behavior (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/2187";>#2187</a>)</li> </ul> <h2><code>@rjsf/mantine</code></h2> <ul> <li>Added <code>ui:autocapitalize</code> support for text inputs (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/2187";>#2187</a>)</li> </ul> <h2><code>@rjsf/mui</code></h2> <ul> <li>Added <code>ui:autocapitalize</code> support for text inputs (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/2187";>#2187</a>)</li> </ul> <h2><code>@rjsf/utils</code></h2> <ul> <li>Fixed <code>sanitizeDataForNewSchema()</code> clearing existing arrays or preserving stale <code>undefined</code> values instead of retaining data or applying defaults for properties newly defined by the incoming schema (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/3736";>#3736</a>)</li> <li>Added <code>autocapitalize</code> UI option handling to <code>getInputProps()</code> and its public input prop types (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/2187";>#2187</a>)</li> </ul> <h2><code>@rjsf/validator-ajv8</code></h2> <ul> <li>Changed the <code>standaloneCode</code> import to name the file, <code>ajv/dist/standalone/index.js</code>, instead of the directory subpath <code>ajv/dist/standalone</code>. A <code>tsc-alias</code> replacer used to patch this into the emitted output; the source now says what it means. No public API changed</li> </ul> <h2>Dev / docs / playground</h2> <ul> <li>Relative TypeScript imports now name their real <code>.ts</code>/<code>.tsx</code> source file (and an explicit <code>index.ts</code> for directory imports), and TypeScript's <code>rewriteRelativeImportExtensions</code> emits the <code>.js</code> specifiers directly. This removes <code>tsc-alias</code> and its post-emit string rewriting entirely, along with the <code>tsc-alias-replacer/</code> directory, both <code>tsconfig.replacer.json</code> files, the <code>compileReplacer</code> scripts and <code>move-file-cli</code>. Naming the source file rather than the output is deliberate: Node's native type stripping requires exact <code>.ts</code> extensions and does no extension or directory-index searching, so this avoids a second repository-wide import migration later</li> <li>Fixed <code>packages/daisyui/test/tsconfig.json</code>, which was configured to emit into <code>../dist</code> — the esbuild/rollup bundle output directory — instead of type-checking without emit like every other test project</li> <li>Collapsed each package's <code>tsconfig.json</code> + <code>tsconfig.build.json</code> + <code>src/tsconfig.json</code> chain into one source config plus one test config extending a new shared root <code>tsconfig.test.json</code>. Building a package no longer pulls its dependencies' test projects into the graph</li> <li>Fixed the root <code>tsconfig.json</code>, which referenced <code>snapshot-tests</code> twice and omitted <code>mantine</code>, <code>primereact</code>, <code>validator-ata</code> and <code>validator-cfworker</code>. It now lists every source and test project once, and a new root <code>typecheck</code> script runs in CI, so tests are typechecked for the first time. That surfaced stale tests in <code>@rjsf/chakra-ui</code> and <code>@rjsf/validator-ata</code> and two drifted playground samples, fixed here. <code>@rjsf/chakra-ui</code>'s <code>type-check</code> script previously ran against a solution config with <code>files: []</code> and checked nothing</li> <li>Every package now emits <code>lib/</code> with the same settings: <code>esnext</code> target plus <code>.js.map</code> and <code>.d.ts.map</code>. Previously only <code>@rjsf/core</code> did; the rest emitted ES2018 with JS source maps only, depending on which root config their <code>src/tsconfig.json</code> extended</li> <li><code>tsconfig.tsbuildinfo</code> is no longer written into <code>lib/</code> and published with it. In 6.8.0 it was 446 kB of <code>@rjsf/antd</code>'s 959 kB unpacked tarball</li> <li>Set <code>"types": []</code> in <code>tsconfig.base.json</code> so packages no longer see every hoisted <code>@types/*</code>, with Node-using packages opting in, and <code>"lib": ["ESNext"]</code> in the three validator packages so they cannot compile against browser globals</li> <li><code>build:ts</code> is now plain <code>tsc -b</code>. The old <code>rimraf ./lib</code> also deleted the build-info, forcing a full rebuild every time; the build-info is now an Nx <code>build</code> output alongside <code>lib/</code> so cache restores stay coherent</li> <li>Added <code>"type": "module"</code> to <code>@rjsf/snapshot-tests</code>, which publishes ESM <code>.js</code> files</li> <li>Enabled <code>verbatimModuleSyntax</code>, so type-only imports must be written as <code>import type</code>. The one import it affected, <code>React</code> in <code>@rjsf/utils</code>'s <code>shouldRender.ts</code>, is now type-only, so emitted output is unchanged</li> <li>Documented <code>ui:autocapitalize</code>, added it to the simple playground sample, and added cross-theme regression coverage (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/2187";>#2187</a>)</li> </ul> <h2>6.9.0</h2> <blockquote> <p><strong>Potentially breaking change:</strong> <code>lodash</code> and <code>lodash-es</code> are no longer dependencies of any <code>@rjsf/*</code> package. No RJSF public API changed, but an application that imports <code>lodash</code> itself without declaring it — relying on it being hoisted into <code>node_modules</code> because RJSF depended on it — must now add <code>lodash</code> to its own <code>package.json</code>.</p> </blockquote> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/rjsf-team/react-jsonschema-form/blob/main/CHANGELOG.md";>@rjsf/utils's changelog</a>.</em></p> <blockquote> <h1>6.10.0</h1> <h2><code>@rjsf/chakra-ui</code></h2> <ul> <li>Removed an <code>environment</code> prop the test wrapper passed to <code>EnvironmentProvider</code>, which has no such prop and silently ignored it</li> </ul> <h2><code>@rjsf/core</code></h2> <ul> <li>Fixed defaults not being restored when returning to an <code>anyOf</code> or <code>oneOf</code> option with disjoint properties (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/3736";>#3736</a>)</li> <li>Added <code>ui:autocapitalize</code> support for inputs rendered by <code>BaseInputTemplate</code>, allowing mobile keyboards to apply the requested capitalization behavior (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/2187";>#2187</a>)</li> </ul> <h2><code>@rjsf/mantine</code></h2> <ul> <li>Added <code>ui:autocapitalize</code> support for text inputs (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/2187";>#2187</a>)</li> </ul> <h2><code>@rjsf/mui</code></h2> <ul> <li>Added <code>ui:autocapitalize</code> support for text inputs (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/2187";>#2187</a>)</li> </ul> <h2><code>@rjsf/utils</code></h2> <ul> <li>Fixed <code>sanitizeDataForNewSchema()</code> clearing existing arrays or preserving stale <code>undefined</code> values instead of retaining data or applying defaults for properties newly defined by the incoming schema (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/3736";>#3736</a>)</li> <li>Added <code>autocapitalize</code> UI option handling to <code>getInputProps()</code> and its public input prop types (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/2187";>#2187</a>)</li> </ul> <h2>Dev / docs / playground</h2> <ul> <li>Documented <code>ui:autocapitalize</code>, added it to the simple playground sample, and added cross-theme regression coverage (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/2187";>#2187</a>)</li> </ul> <h2><code>@rjsf/validator-ajv8</code></h2> <ul> <li>Changed the <code>standaloneCode</code> import to name the file, <code>ajv/dist/standalone/index.js</code>, instead of the directory subpath <code>ajv/dist/standalone</code>. A <code>tsc-alias</code> replacer used to patch this into the emitted output; the source now says what it means. No public API changed</li> </ul> <h2>Dev / docs / playground</h2> <ul> <li>Relative TypeScript imports now name their real <code>.ts</code>/<code>.tsx</code> source file (and an explicit <code>index.ts</code> for directory imports), and TypeScript's <code>rewriteRelativeImportExtensions</code> emits the <code>.js</code> specifiers directly. This removes <code>tsc-alias</code> and its post-emit string rewriting entirely, along with the <code>tsc-alias-replacer/</code> directory, both <code>tsconfig.replacer.json</code> files, the <code>compileReplacer</code> scripts and <code>move-file-cli</code>. Naming the source file rather than the output is deliberate: Node's native type stripping requires exact <code>.ts</code> extensions and does no extension or directory-index searching, so this avoids a second repository-wide import migration later</li> <li>Fixed <code>packages/daisyui/test/tsconfig.json</code>, which was configured to emit into <code>../dist</code> — the esbuild/rollup bundle output directory — instead of type-checking without emit like every other test project</li> <li>Collapsed each package's <code>tsconfig.json</code> + <code>tsconfig.build.json</code> + <code>src/tsconfig.json</code> chain into one source config plus one test config extending a new shared root <code>tsconfig.test.json</code>. Building a package no longer pulls its dependencies' test projects into the graph</li> <li>Fixed the root <code>tsconfig.json</code>, which referenced <code>snapshot-tests</code> twice and omitted <code>mantine</code>, <code>primereact</code>, <code>validator-ata</code> and <code>validator-cfworker</code>. It now lists every source and test project once, and a new root <code>typecheck</code> script runs in CI, so tests are typechecked for the first time. That surfaced stale tests in <code>@rjsf/chakra-ui</code> and <code>@rjsf/validator-ata</code> and two drifted playground samples, fixed here. <code>@rjsf/chakra-ui</code>'s <code>type-check</code> script previously ran against a solution config with <code>files: []</code> and checked nothing</li> <li>Every package now emits <code>lib/</code> with the same settings: <code>esnext</code> target plus <code>.js.map</code> and <code>.d.ts.map</code>. Previously only <code>@rjsf/core</code> did; the rest emitted ES2018 with JS source maps only, depending on which root config their <code>src/tsconfig.json</code> extended</li> <li><code>tsconfig.tsbuildinfo</code> is no longer written into <code>lib/</code> and published with it. In 6.8.0 it was 446 kB of <code>@rjsf/antd</code>'s 959 kB unpacked tarball</li> <li>Set <code>"types": []</code> in <code>tsconfig.base.json</code> so packages no longer see every hoisted <code>@types/*</code>, with Node-using packages opting in, and <code>"lib": ["ESNext"]</code> in the three validator packages so they cannot compile against browser globals</li> <li><code>build:ts</code> is now plain <code>tsc -b</code>. The old <code>rimraf ./lib</code> also deleted the build-info, forcing a full rebuild every time; the build-info is now an Nx <code>build</code> output alongside <code>lib/</code> so cache restores stay coherent</li> <li>Added <code>"type": "module"</code> to <code>@rjsf/snapshot-tests</code>, which publishes ESM <code>.js</code> files</li> <li>Enabled <code>verbatimModuleSyntax</code>, so type-only imports must be written as <code>import type</code>. The one import it affected, <code>React</code> in <code>@rjsf/utils</code>'s <code>shouldRender.ts</code>, is now type-only, so emitted output is unchanged</li> </ul> <h1>6.9.0</h1> <blockquote> <p><strong>Potentially breaking change:</strong> <code>lodash</code> and <code>lodash-es</code> are no longer dependencies of any <code>@rjsf/*</code> package. No RJSF public API changed, but an application that imports <code>lodash</code> itself without declaring it — relying on it being hoisted into <code>node_modules</code> because RJSF depended on it — must now add <code>lodash</code> to its own <code>package.json</code>.</p> </blockquote> <h2><code>@rjsf/antd</code></h2> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/rjsf-team/react-jsonschema-form/commit/014f2e0ec4201e8b2f0244be49563101846f8814";><code>014f2e0</code></a> Releasing 6.10.0</li> <li><a href="https://github.com/rjsf-team/react-jsonschema-form/commit/d23f31e3dd80eb39d06183cef0c17f771b4f67cf";><code>d23f31e</code></a> Upgrade Nx and fix failing release (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/5251";>#5251</a>)</li> <li><a href="https://github.com/rjsf-team/react-jsonschema-form/commit/bc9feedd4e34fe2c3798d94b92d23d9adb44df1f";><code>bc9feed</code></a> feat: support ui:autocapitalize (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/5240";>#5240</a>)</li> <li><a href="https://github.com/rjsf-team/react-jsonschema-form/commit/1a2bb662b79dc28156a83eccfffb91fc33dac3b2";><code>1a2bb66</code></a> build: one tsconfig per package, typecheck tests in CI, stop publishing tsbui...</li> <li><a href="https://github.com/rjsf-team/react-jsonschema-form/commit/bd1775eac7833de74f3fde387aafca952b481c05";><code>bd1775e</code></a> chore(deps): bump fast-uri from 4.1.3 to 4.1.4 (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/5239";>#5239</a>)</li> <li><a href="https://github.com/rjsf-team/react-jsonschema-form/commit/e0f36c9434cc3e187e6f3d4ec9990fccac44a568";><code>e0f36c9</code></a> build: import real .ts/.tsx paths in source and drop tsc-alias (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/5233";>#5233</a>)</li> <li><a href="https://github.com/rjsf-team/react-jsonschema-form/commit/67def97b49881ebab977a7f42359f03ad02f1e76";><code>67def97</code></a> fix(utils): Use defaults when toggling between oneOf/anyOf schemas (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/5218";>#5218</a>)</li> <li><a href="https://github.com/rjsf-team/react-jsonschema-form/commit/84c424e0c76ef4417ebb45e5523987ae0140bdbc";><code>84c424e</code></a> Releasing 6.9.0 (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/5234";>#5234</a>)</li> <li><a href="https://github.com/rjsf-team/react-jsonschema-form/commit/dc056e2de677613247f015258fc46ee6263ce807";><code>dc056e2</code></a> Fixes related to empty values (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/5222";>#5222</a>) (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/5225";>#5225</a>)</li> <li><a href="https://github.com/rjsf-team/react-jsonschema-form/commit/b569fc64cfe8e68d95d6e3d1d14d8e4ec52473ba";><code>b569fc6</code></a> test: resolve workspace packages from source via an <code>@rjsf/source</code> export condi...</li> <li>Additional commits viewable in <a href="https://github.com/rjsf-team/react-jsonschema-form/compare/v6.8.0...v6.10.0";>compare view</a></li> </ul> </details> <br /> Updates `@rjsf/validator-ajv8` from 6.8.0 to 6.10.0 <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/rjsf-team/react-jsonschema-form/releases";>@rjsf/validator-ajv8's releases</a>.</em></p> <blockquote> <h2>6.10.0</h2> <h1>New Feature added</h1> <p><a href="https://rjsf-team.github.io/react-jsonschema-form/docs/api-reference/uiSchema#autocapitalize";>autocapitalize</a> support was added to the uiSchema</p> <p>Also, since 6.9.0 failed to release properly, this also contains all of its <a href="https://github.com/rjsf-team/react-jsonschema-form/releases/tag/v6.9.0";>content</a></p> <h2><code>@rjsf/chakra-ui</code></h2> <ul> <li>Removed an <code>environment</code> prop the test wrapper passed to <code>EnvironmentProvider</code>, which has no such prop and silently ignored it</li> </ul> <h2><code>@rjsf/core</code></h2> <ul> <li>Fixed defaults not being restored when returning to an <code>anyOf</code> or <code>oneOf</code> option with disjoint properties (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/3736";>#3736</a>)</li> <li>Added <code>ui:autocapitalize</code> support for inputs rendered by <code>BaseInputTemplate</code>, allowing mobile keyboards to apply the requested capitalization behavior (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/2187";>#2187</a>)</li> </ul> <h2><code>@rjsf/mantine</code></h2> <ul> <li>Added <code>ui:autocapitalize</code> support for text inputs (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/2187";>#2187</a>)</li> </ul> <h2><code>@rjsf/mui</code></h2> <ul> <li>Added <code>ui:autocapitalize</code> support for text inputs (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/2187";>#2187</a>)</li> </ul> <h2><code>@rjsf/utils</code></h2> <ul> <li>Fixed <code>sanitizeDataForNewSchema()</code> clearing existing arrays or preserving stale <code>undefined</code> values instead of retaining data or applying defaults for properties newly defined by the incoming schema (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/3736";>#3736</a>)</li> <li>Added <code>autocapitalize</code> UI option handling to <code>getInputProps()</code> and its public input prop types (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/2187";>#2187</a>)</li> </ul> <h2><code>@rjsf/validator-ajv8</code></h2> <ul> <li>Changed the <code>standaloneCode</code> import to name the file, <code>ajv/dist/standalone/index.js</code>, instead of the directory subpath <code>ajv/dist/standalone</code>. A <code>tsc-alias</code> replacer used to patch this into the emitted output; the source now says what it means. No public API changed</li> </ul> <h2>Dev / docs / playground</h2> <ul> <li>Relative TypeScript imports now name their real <code>.ts</code>/<code>.tsx</code> source file (and an explicit <code>index.ts</code> for directory imports), and TypeScript's <code>rewriteRelativeImportExtensions</code> emits the <code>.js</code> specifiers directly. This removes <code>tsc-alias</code> and its post-emit string rewriting entirely, along with the <code>tsc-alias-replacer/</code> directory, both <code>tsconfig.replacer.json</code> files, the <code>compileReplacer</code> scripts and <code>move-file-cli</code>. Naming the source file rather than the output is deliberate: Node's native type stripping requires exact <code>.ts</code> extensions and does no extension or directory-index searching, so this avoids a second repository-wide import migration later</li> <li>Fixed <code>packages/daisyui/test/tsconfig.json</code>, which was configured to emit into <code>../dist</code> — the esbuild/rollup bundle output directory — instead of type-checking without emit like every other test project</li> <li>Collapsed each package's <code>tsconfig.json</code> + <code>tsconfig.build.json</code> + <code>src/tsconfig.json</code> chain into one source config plus one test config extending a new shared root <code>tsconfig.test.json</code>. Building a package no longer pulls its dependencies' test projects into the graph</li> <li>Fixed the root <code>tsconfig.json</code>, which referenced <code>snapshot-tests</code> twice and omitted <code>mantine</code>, <code>primereact</code>, <code>validator-ata</code> and <code>validator-cfworker</code>. It now lists every source and test project once, and a new root <code>typecheck</code> script runs in CI, so tests are typechecked for the first time. That surfaced stale tests in <code>@rjsf/chakra-ui</code> and <code>@rjsf/validator-ata</code> and two drifted playground samples, fixed here. <code>@rjsf/chakra-ui</code>'s <code>type-check</code> script previously ran against a solution config with <code>files: []</code> and checked nothing</li> <li>Every package now emits <code>lib/</code> with the same settings: <code>esnext</code> target plus <code>.js.map</code> and <code>.d.ts.map</code>. Previously only <code>@rjsf/core</code> did; the rest emitted ES2018 with JS source maps only, depending on which root config their <code>src/tsconfig.json</code> extended</li> <li><code>tsconfig.tsbuildinfo</code> is no longer written into <code>lib/</code> and published with it. In 6.8.0 it was 446 kB of <code>@rjsf/antd</code>'s 959 kB unpacked tarball</li> <li>Set <code>"types": []</code> in <code>tsconfig.base.json</code> so packages no longer see every hoisted <code>@types/*</code>, with Node-using packages opting in, and <code>"lib": ["ESNext"]</code> in the three validator packages so they cannot compile against browser globals</li> <li><code>build:ts</code> is now plain <code>tsc -b</code>. The old <code>rimraf ./lib</code> also deleted the build-info, forcing a full rebuild every time; the build-info is now an Nx <code>build</code> output alongside <code>lib/</code> so cache restores stay coherent</li> <li>Added <code>"type": "module"</code> to <code>@rjsf/snapshot-tests</code>, which publishes ESM <code>.js</code> files</li> <li>Enabled <code>verbatimModuleSyntax</code>, so type-only imports must be written as <code>import type</code>. The one import it affected, <code>React</code> in <code>@rjsf/utils</code>'s <code>shouldRender.ts</code>, is now type-only, so emitted output is unchanged</li> <li>Documented <code>ui:autocapitalize</code>, added it to the simple playground sample, and added cross-theme regression coverage (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/2187";>#2187</a>)</li> </ul> <h2>6.9.0</h2> <blockquote> <p><strong>Potentially breaking change:</strong> <code>lodash</code> and <code>lodash-es</code> are no longer dependencies of any <code>@rjsf/*</code> package. No RJSF public API changed, but an application that imports <code>lodash</code> itself without declaring it — relying on it being hoisted into <code>node_modules</code> because RJSF depended on it — must now add <code>lodash</code> to its own <code>package.json</code>.</p> </blockquote> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/rjsf-team/react-jsonschema-form/blob/main/CHANGELOG.md";>@rjsf/validator-ajv8's changelog</a>.</em></p> <blockquote> <h1>6.10.0</h1> <h2><code>@rjsf/chakra-ui</code></h2> <ul> <li>Removed an <code>environment</code> prop the test wrapper passed to <code>EnvironmentProvider</code>, which has no such prop and silently ignored it</li> </ul> <h2><code>@rjsf/core</code></h2> <ul> <li>Fixed defaults not being restored when returning to an <code>anyOf</code> or <code>oneOf</code> option with disjoint properties (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/3736";>#3736</a>)</li> <li>Added <code>ui:autocapitalize</code> support for inputs rendered by <code>BaseInputTemplate</code>, allowing mobile keyboards to apply the requested capitalization behavior (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/2187";>#2187</a>)</li> </ul> <h2><code>@rjsf/mantine</code></h2> <ul> <li>Added <code>ui:autocapitalize</code> support for text inputs (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/2187";>#2187</a>)</li> </ul> <h2><code>@rjsf/mui</code></h2> <ul> <li>Added <code>ui:autocapitalize</code> support for text inputs (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/2187";>#2187</a>)</li> </ul> <h2><code>@rjsf/utils</code></h2> <ul> <li>Fixed <code>sanitizeDataForNewSchema()</code> clearing existing arrays or preserving stale <code>undefined</code> values instead of retaining data or applying defaults for properties newly defined by the incoming schema (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/3736";>#3736</a>)</li> <li>Added <code>autocapitalize</code> UI option handling to <code>getInputProps()</code> and its public input prop types (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/2187";>#2187</a>)</li> </ul> <h2>Dev / docs / playground</h2> <ul> <li>Documented <code>ui:autocapitalize</code>, added it to the simple playground sample, and added cross-theme regression coverage (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/2187";>#2187</a>)</li> </ul> <h2><code>@rjsf/validator-ajv8</code></h2> <ul> <li>Changed the <code>standaloneCode</code> import to name the file, <code>ajv/dist/standalone/index.js</code>, instead of the directory subpath <code>ajv/dist/standalone</code>. A <code>tsc-alias</code> replacer used to patch this into the emitted output; the source now says what it means. No public API changed</li> </ul> <h2>Dev / docs / playground</h2> <ul> <li>Relative TypeScript imports now name their real <code>.ts</code>/<code>.tsx</code> source file (and an explicit <code>index.ts</code> for directory imports), and TypeScript's <code>rewriteRelativeImportExtensions</code> emits the <code>.js</code> specifiers directly. This removes <code>tsc-alias</code> and its post-emit string rewriting entirely, along with the <code>tsc-alias-replacer/</code> directory, both <code>tsconfig.replacer.json</code> files, the <code>compileReplacer</code> scripts and <code>move-file-cli</code>. Naming the source file rather than the output is deliberate: Node's native type stripping requires exact <code>.ts</code> extensions and does no extension or directory-index searching, so this avoids a second repository-wide import migration later</li> <li>Fixed <code>packages/daisyui/test/tsconfig.json</code>, which was configured to emit into <code>../dist</code> — the esbuild/rollup bundle output directory — instead of type-checking without emit like every other test project</li> <li>Collapsed each package's <code>tsconfig.json</code> + <code>tsconfig.build.json</code> + <code>src/tsconfig.json</code> chain into one source config plus one test config extending a new shared root <code>tsconfig.test.json</code>. Building a package no longer pulls its dependencies' test projects into the graph</li> <li>Fixed the root <code>tsconfig.json</code>, which referenced <code>snapshot-tests</code> twice and omitted <code>mantine</code>, <code>primereact</code>, <code>validator-ata</code> and <code>validator-cfworker</code>. It now lists every source and test project once, and a new root <code>typecheck</code> script runs in CI, so tests are typechecked for the first time. That surfaced stale tests in <code>@rjsf/chakra-ui</code> and <code>@rjsf/validator-ata</code> and two drifted playground samples, fixed here. <code>@rjsf/chakra-ui</code>'s <code>type-check</code> script previously ran against a solution config with <code>files: []</code> and checked nothing</li> <li>Every package now emits <code>lib/</code> with the same settings: <code>esnext</code> target plus <code>.js.map</code> and <code>.d.ts.map</code>. Previously only <code>@rjsf/core</code> did; the rest emitted ES2018 with JS source maps only, depending on which root config their <code>src/tsconfig.json</code> extended</li> <li><code>tsconfig.tsbuildinfo</code> is no longer written into <code>lib/</code> and published with it. In 6.8.0 it was 446 kB of <code>@rjsf/antd</code>'s 959 kB unpacked tarball</li> <li>Set <code>"types": []</code> in <code>tsconfig.base.json</code> so packages no longer see every hoisted <code>@types/*</code>, with Node-using packages opting in, and <code>"lib": ["ESNext"]</code> in the three validator packages so they cannot compile against browser globals</li> <li><code>build:ts</code> is now plain <code>tsc -b</code>. The old <code>rimraf ./lib</code> also deleted the build-info, forcing a full rebuild every time; the build-info is now an Nx <code>build</code> output alongside <code>lib/</code> so cache restores stay coherent</li> <li>Added <code>"type": "module"</code> to <code>@rjsf/snapshot-tests</code>, which publishes ESM <code>.js</code> files</li> <li>Enabled <code>verbatimModuleSyntax</code>, so type-only imports must be written as <code>import type</code>. The one import it affected, <code>React</code> in <code>@rjsf/utils</code>'s <code>shouldRender.ts</code>, is now type-only, so emitted output is unchanged</li> </ul> <h1>6.9.0</h1> <blockquote> <p><strong>Potentially breaking change:</strong> <code>lodash</code> and <code>lodash-es</code> are no longer dependencies of any <code>@rjsf/*</code> package. No RJSF public API changed, but an application that imports <code>lodash</code> itself without declaring it — relying on it being hoisted into <code>node_modules</code> because RJSF depended on it — must now add <code>lodash</code> to its own <code>package.json</code>.</p> </blockquote> <h2><code>@rjsf/antd</code></h2> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/rjsf-team/react-jsonschema-form/commit/014f2e0ec4201e8b2f0244be49563101846f8814";><code>014f2e0</code></a> Releasing 6.10.0</li> <li><a href="https://github.com/rjsf-team/react-jsonschema-form/commit/d23f31e3dd80eb39d06183cef0c17f771b4f67cf";><code>d23f31e</code></a> Upgrade Nx and fix failing release (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/5251";>#5251</a>)</li> <li><a href="https://github.com/rjsf-team/react-jsonschema-form/commit/bc9feedd4e34fe2c3798d94b92d23d9adb44df1f";><code>bc9feed</code></a> feat: support ui:autocapitalize (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/5240";>#5240</a>)</li> <li><a href="https://github.com/rjsf-team/react-jsonschema-form/commit/1a2bb662b79dc28156a83eccfffb91fc33dac3b2";><code>1a2bb66</code></a> build: one tsconfig per package, typecheck tests in CI, stop publishing tsbui...</li> <li><a href="https://github.com/rjsf-team/react-jsonschema-form/commit/bd1775eac7833de74f3fde387aafca952b481c05";><code>bd1775e</code></a> chore(deps): bump fast-uri from 4.1.3 to 4.1.4 (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/5239";>#5239</a>)</li> <li><a href="https://github.com/rjsf-team/react-jsonschema-form/commit/e0f36c9434cc3e187e6f3d4ec9990fccac44a568";><code>e0f36c9</code></a> build: import real .ts/.tsx paths in source and drop tsc-alias (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/5233";>#5233</a>)</li> <li><a href="https://github.com/rjsf-team/react-jsonschema-form/commit/67def97b49881ebab977a7f42359f03ad02f1e76";><code>67def97</code></a> fix(utils): Use defaults when toggling between oneOf/anyOf schemas (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/5218";>#5218</a>)</li> <li><a href="https://github.com/rjsf-team/react-jsonschema-form/commit/84c424e0c76ef4417ebb45e5523987ae0140bdbc";><code>84c424e</code></a> Releasing 6.9.0 (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/5234";>#5234</a>)</li> <li><a href="https://github.com/rjsf-team/react-jsonschema-form/commit/dc056e2de677613247f015258fc46ee6263ce807";><code>dc056e2</code></a> Fixes related to empty values (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/5222";>#5222</a>) (<a href="https://redirect.github.com/rjsf-team/react-jsonschema-form/issues/5225";>#5225</a>)</li> <li><a href="https://github.com/rjsf-team/react-jsonschema-form/commit/b569fc64cfe8e68d95d6e3d1d14d8e4ec52473ba";><code>b569fc6</code></a> test: resolve workspace packages from source via an <code>@rjsf/source</code> export condi...</li> <li>Additional commits viewable in <a href="https://github.com/rjsf-team/react-jsonschema-form/compare/v6.8.0...v6.10.0";>compare view</a></li> </ul> </details> <br /> 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> 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 </details> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
