Skip to content

fix(schema): allow chaining maxFileSize/types after maxFiles #534

fix(schema): allow chaining maxFileSize/types after maxFiles

fix(schema): allow chaining maxFileSize/types after maxFiles #534

Triggered via pull request April 7, 2026 19:50
Status Success
Total duration 2m 1s
Artifacts 1

ci.yml

on: pull_request
🛡️ Quality Gates
36s
🛡️ Quality Gates
🏗️ Build & Bundle Analysis
44s
🏗️ Build & Bundle Analysis
🔐 Security Audit
21s
🔐 Security Audit
Matrix: compatibility
✅ All Checks Passed
3s
✅ All Checks Passed
Fit to window
Zoom out
Zoom in

Annotations

16 warnings
🛡️ Quality Gates
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea, actions/setup-node@v4, pnpm/action-setup@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
🛡️ Quality Gates: packages/ui/scripts/build-registry.ts#L44
'error' is defined but never used
🛡️ Quality Gates: packages/ui/scripts/build-registry.ts#L9
'registryDir' is assigned a value but never used
🛡️ Quality Gates: packages/ui/registry/default/upload-dropzone/upload-dropzone.tsx#L84
'index' is defined but never used. Allowed unused args must match /^_/u
🛡️ Quality Gates: packages/ui/registry/default/upload-dropzone/upload-dropzone.tsx#L57
'files' is assigned a value but never used
🛡️ Quality Gates: packages/ui/registry/default/upload-demo/upload-demo.tsx#L73
Unexpected any. Specify a different type
🛡️ Quality Gates: packages/ui/registry/default/upload-demo/upload-demo.tsx#L59
'handleUploadProgress' is assigned a value but never used
🛡️ Quality Gates: packages/ui/registry/default/upload-demo/upload-demo.tsx#L28
Unexpected any. Specify a different type
🛡️ Quality Gates: packages/ui/registry/default/upload-button/upload-button.tsx#L20
Unexpected any. Specify a different type
🔐 Security Audit
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@v4, pnpm/action-setup@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
🏗️ Build & Bundle Analysis
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-node@v4, actions/upload-artifact@v5, pnpm/action-setup@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
🎯 Node.js 18 Compatibility
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6, actions/setup-node@v4, pnpm/action-setup@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
🎯 Node.js 20 Compatibility
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6, actions/setup-node@v4, pnpm/action-setup@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
🎯 Node.js 22 Compatibility
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/download-artifact@v6, actions/setup-node@v4, pnpm/action-setup@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Artifacts

Produced during runtime
Name Size Digest
build-artifacts Expired
119 KB
sha256:c585ebcfbf4f74a0e68752544ab9eb723e1a21f88052237859e1579d23833cb7