deps: bump storybook - #31
Conversation
- esbuild 0.28.1 → 0.28.2 (cascades through vite, vitest, storybook) - baseline-browser-mapping 2.11.12 → 2.11.13
There was a problem hiding this comment.
Copilot wasn't able to review any files in this pull request.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
|
Important Review skippedReview was skipped due to path filters ⛔ Files ignored due to path filters (1)
CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Fallow audit reportNo GitHub PR/MR findings. Generated by fallow. |
Summary
0.28.1to0.28.2innub.lock(patch-level, within the same0.28minor).vite,vite-plus,vitest+ browser runners,@vitejs/plugin-react,@storybook/*(addon-docs, addon-vitest, react-vite, builder-vite, csf-plugin),@inlang/paraglide-js, and the full set of platform-specific@esbuild/*optional binaries.baseline-browser-mapping2.11.12→2.11.13.package.jsonspecifiers altered; existing ranges continue to resolve cleanly.Testing
nub ci— reinstall resolves the lockfile without drift.mise run test:ci— full monorepo test suite (matches the Test workflow).mise run ci— hk quality checks (lint, typecheck, format, Fallow/steiger) against the updated tree.mise run build/mise run build:cf-pages— confirm build pipelines (Vite/esbuild-driven) still produce artifacts.