Bump the prod-dependencies-minor group with 6 updates

[dependabot]

Bumps the prod-dependencies-minor group with 6 updates:

Package	From	To
@floating-ui/react	0.26.28	0.27.3
css-tree	3.0.1	3.1.0
debug	4.3.7	4.4.0
papaparse	5.4.1	5.5.2
react-zoom-pan-pinch	3.6.1	3.7.0
yaml	2.6.1	2.7.0

Updates @floating-ui/react from 0.26.28 to 0.27.3

Release notes

Sourced from @​floating-ui/react's releases.

@​floating-ui/react@​0.27.3

Patch Changes

• feat(FloatingFocusManager): accept FloatingRootContext as the context prop
• fix(useListNavigation): check for virtual pointer on pointerenter
• refactor: use jsx runtime
• Update dependencies: @floating-ui/[email protected]

@​floating-ui/react@​0.27.2

Patch Changes

• fix(FloatingFocusManager): prevent stale inert/aria-hidden attributes from being left on outside elements

@​floating-ui/react@​0.27.1

Patch Changes

• fix(FloatingFocusManager): correctly fallback to container
• fix(FloatingFocusManager): check for ancestor floating focus element during closeOnFocusOut
• fix(FloatingFocusManager): avoid marking tree ancestor floating nodes with data-floating-ui-inert when modal=false

@​floating-ui/react@​0.27.0

Minor Changes

• chore: deprecate inner and useInnerOffset. This technique of aligning an inner element to the reference has poor performance with longer lists, doesn't fit with the middleware paradigm, doesn't work on touch, and has a better custom alternative using native onScroll that is encouraged instead.
• breaking: drop React 16 support. 17 is the minimum supported version.
• fix(useId): add | undefined return type for React 17

Patch Changes

• feat(FloatingFocusManager): add outsideElementsInert prop. This enables pointer modality without a backdrop.
• perf(useListNavigation): simplify focusing to remove unneeded asynchronicity
• fix(useDismiss): allow native clicks to work with referencePress
• fix(useDismiss): read target overflow style for scrollbar press check. Fixes an issue where outside presses would be incorrectly prevented if the target element that was pressed appeared scrollable but was actually not.
• fix(FloatingFocusManager): check for 'safe-polygon' reason on return focus

Changelog

Sourced from @​floating-ui/react's changelog.

0.27.3

Patch Changes

• feat(FloatingFocusManager): accept FloatingRootContext as the context prop
• fix(useListNavigation): check for virtual pointer on pointerenter
• refactor: use jsx runtime
• Update dependencies: @floating-ui/[email protected]

0.27.2

Patch Changes

• fix(FloatingFocusManager): prevent stale inert/aria-hidden attributes from being left on outside elements

0.27.1

Patch Changes

• fix(FloatingFocusManager): correctly fallback to container
• fix(FloatingFocusManager): check for ancestor floating focus element during closeOnFocusOut
• fix(FloatingFocusManager): avoid marking tree ancestor floating nodes with data-floating-ui-inert when modal=false

0.27.0

Minor Changes

• chore: deprecate inner and useInnerOffset. This technique of aligning an inner element to the reference has poor performance with longer lists, doesn't fit with the middleware paradigm, doesn't work on touch, and has a better custom alternative using native onScroll that is encouraged instead.
• breaking: drop React 16 support. 17 is the minimum supported version.
• fix(useId): add | undefined return type for React 17

Patch Changes

• feat(FloatingFocusManager): add outsideElementsInert prop. This enables pointer modality without a backdrop.
• perf(useListNavigation): simplify focusing to remove unneeded asynchronicity
• fix(useDismiss): allow native clicks to work with referencePress
• fix(useDismiss): read target overflow style for scrollbar press check. Fixes an issue where outside presses would be incorrectly prevented if the target element that was pressed appeared scrollable but was actually not.
• fix(FloatingFocusManager): check for 'safe-polygon' reason on return focus

Commits

• b0dfb58 chore: version packages (#3187)
• 1fa2c50 chore(eslint): add 'eslint-plugin-prettier', apply 'prettier' rules (#3177)
• 69b5f88 feat(FloatingFocusManager): accept FloatingRootContext (#3182)
• b6d88be fix(useListNavigation): check for virtual pointer on pointerenter (#3184)
• 568eab7 refactor: use jsx runtime (#3186)
• 6a9f758 chore: version packages (#3165)
• c9f19ec fix(FloatingFocusManager): prevent stale inert/aria-hidden attributes fro...
• 33bd900 chore: version packages (#3158)
• e24b4fb fix(FloatingFocusManager): avoid marking tree ancestor floating nodes when `m...
• c728afa fix(FloatingFocusManager): check for floating focus root element (#3159)
• Additional commits viewable in compare view

Updates css-tree from 3.0.1 to 3.1.0

Release notes

Sourced from css-tree's releases.

3.1.0

• Added support for boolean expression multiplier in syntax definition, i.e. <boolean-expr[ test ]> (#304)
• Added source, startOffset, startLine, and startColumn parameters to OffsetToLocation constructor, eliminating the need to call setSource() after creating a new OffsetToLocation instance
• Exposed OffsetToLocation class in the main entry point, which was previously accessible only via css-tree/tokenizer
• Fixed Raw node value consumption by ignoring stop tokens inside blocks, resolving an issue where Raw value consumption stopped prematurely. This fix also enables parsing of functions whose content includes stop characters (e.g., semicolons and curly braces) within declaration values, aligning with the latest draft of CSS Values and Units L5.
• Fixed TokenStream#balance computation to handle unmatched brackets correctly. Previously, when encountering a closing bracket, the TokenStream would prioritize it over unmatched opening brackets, leading to improper parsing. For example, the parser would incorrectly consume the declaration value of .a { prop: ([{); } as ([{) instead of consuming it until all opened brackets were closed (([{); }). Now, unmatched closing brackets are discarded unless they match the most recent opening bracket on the stack. This change aligns CSSTree with CSS specifications and browser behavior.
• Fixed syntax definition parser to allow a token to be followed by a multiplier (#303)
• Fixed location for Layer node (#310)
• Bumped mdn/data to 2.12.2

Changelog

Sourced from css-tree's changelog.

3.1.0 (December 6, 2024)

• Added support for boolean expression multiplier in syntax definition, i.e. <boolean-expr[ test ]> (#304)
• Added source, startOffset, startLine, and startColumn parameters to OffsetToLocation constructor, eliminating the need to call setSource() after creating a new OffsetToLocation instance
• Exposed OffsetToLocation class in the main entry point, which was previously accessible only via css-tree/tokenizer
• Fixed Raw node value consumption by ignoring stop tokens inside blocks, resolving an issue where Raw value consumption stopped prematurely. This fix also enables parsing of functions whose content includes stop characters (e.g., semicolons and curly braces) within declaration values, aligning with the latest draft of CSS Values and Units Module Level 5.
• Fixed TokenStream#balance computation to handle unmatched brackets correctly. Previously, when encountering a closing bracket, the TokenStream would prioritize it over unmatched opening brackets, leading to improper parsing. For example, the parser would incorrectly consume the declaration value of .a { prop: ([{); } as ([{) instead of consuming it until all opened brackets were closed (([{); }). Now, unmatched closing brackets are discarded unless they match the most recent opening bracket on the stack. This change aligns CSSTree with CSS specifications and browser behavior.
• Fixed syntax definition parser to allow a token to be followed by a multiplier (#303)
• Fixed location for Layer node (#310)
• Bumped mdn/data to 2.12.2

Commits

• 354254f 3.1.0
• 3e0b93b Fix TokenStream#balance computation and
• 6b24dcc Fix npm audit warning
• 758ccf7 Fix location of <layer-name> (#310)
• 7cfec03 Bump esbuild to ^0.24.0
• eab1c8e Add source, startOffset, startLine, and startColumn parameters to `Of...
• ab29676 Expose OffsetToLocation in main entry point
• 0afee3d Update mdn-data to v2.12.2 (#306)
• 2c95a51 Add lexer can check at-rules syntax
• 511bed5 Rename <boolean[]> into <boolean-expr[]> (fixes #307)
• Additional commits viewable in compare view

Updates debug from 4.3.7 to 4.4.0

Release notes

Sourced from debug's releases.

4.4.0

Fixes (hopefully) the inefficient regex warnings in .enable().

Minor version as this is invariably going to break certain users who misuse the .enable() API and expected it to work with regexes, which was never supported nor documented. That's on you, sorry - that functionality won't be added back.

Full Changelog: debug-js/debug@4.3.7...4.4.0

Commits

• 7e3814c 4.4.0
• d2d6bf0 fix inefficient .enable() regex and .enabled() test
• See full diff in compare view

Updates papaparse from 5.4.1 to 5.5.2

Commits

• See full diff in compare view

Updates react-zoom-pan-pinch from 3.6.1 to 3.7.0

Release notes

Sourced from react-zoom-pan-pinch's releases.

v3.7.0

3.7.0 (2025-01-31)

Bug Fixes

• 🐛 lint (ab348dc)
• Fixed auto align to bounds bugs (#486) (3643a47)
• Fixes blurry images on safari. (#497) (5cf057b)
• zoom does not work when pinching on mobile (#499) (d770efb)

Features

• Support auto align to bounds on resize (#485) (800beb1)

Commits

• 68616a3 test: 💍 resize observer polyfill
• ab348dc fix: 🐛 lint
• d770efb fix: zoom does not work when pinching on mobile (#499)
• 5cf057b fix: Fixes blurry images on safari. (#497)
• 3643a47 fix: Fixed auto align to bounds bugs (#486)
• 800beb1 feat: Support auto align to bounds on resize (#485)
• See full diff in compare view

Updates yaml from 2.6.1 to 2.7.0

Release notes

Sourced from yaml's releases.

v2.7.0

The library is now available on JSR as @​eemeli/yaml and on deno.land/x as yaml. In addition to Node.js and browsers, it should work in Deno, Bun, and Cloudflare Workers.

• Use .ts extension in all relative imports (#591)
• Ignore newline after block seq indicator as space before value (#590)
• Require Node.js 14.18 or later (was 14.6) (#598)

Commits

• 8f512b5 2.7.0
• 8a7569a ci: Add jsr.jsonc & jsr-publish workflow
• 8ef085f docs: Fix API docs links
• 374c19c style: Really use explicit imports for process.env and Buffer
• 1ab037d style: Include explicit type declarations on all public APIs
• 4354c42 style: Use explicit imports for process.env and Buffer
• 2c55723 Merge pull request #591 from eemeli/import-ts
• ab240c1 fix: Drop .ts extension from import & export paths in .d.ts files
• c4c49f9 fix: Use separate rather than inline type keyword for TS compatibility
• 3bec004 ci: Add deno smoke test
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @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

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.