chore(deps): bump react-dropzone from 14.3.8 to 14.4.0 in /apps/admin

[dependabot]

Bumps react-dropzone from 14.3.8 to 14.4.0.

Release notes

Sourced from react-dropzone's releases.

v14.4.0

14.4.0 (2026-01-29)

Bug Fixes

• accept files with empty type during drag events (eaa8ba5)
• correct dragLeave filter logic and add dragend test (273aff4)

Features

• add isDragGlobal state for document-level drag detection (f0874b0)

Commits

• e2ae36d build: remove @​semantic-release/git
• 84ff2d6 build: update deps for semantic-release and node version
• 65095ea build: add --ignore-engines flag to test workflow for Node 18 compatibility
• d70ea96 build: enable passwordless publishing with NPM trusted publishers
• 2c2c56e build: add full git history fetch and build step to release workflow
• a9e9741 build: add semantic-release configuration with trusted publishing support
• 1455f4c build: Update checkout action to version 4 in release workflow
• f4e6706 build: Update Node.js setup action to version 4
• 8de653a build: Remove NPM_TOKEN from release.yml
• ca30590 build: Update release.yml to include permissions
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for react-dropzone since your current version.

You can trigger a rebase of this PR 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 this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[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.

• 🔍 Trigger a full review

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[fingertips18]

@coderabbitai Are there any breaking changes in this dependency update? Is it safe to merge?

[coderabbitai]

Tip

For best results, initiate chat on the files or code changes.

@fingertips18: Based on the release notes, there are no breaking changes in this update. Here's my analysis:

Changes in v14.4.0:

1. Bug Fixes:

   • Accept files with empty type during drag events
   • Correct dragLeave filter logic

2. New Feature:

   • Added isDragGlobal state for document-level drag detection

Safety Assessment:

✅ Safe to merge - This is a minor version update (14.3.8 → 14.4.0) that follows semantic versioning conventions:

• Bug fixes improve existing functionality without breaking the API
• The new isDragGlobal feature is additive - it adds a new state property that your existing code doesn't need to use
• No deprecations or removed features are mentioned

Recommendation:

The update should be backward compatible with your current implementation. If your code doesn't reference isDragGlobal, you'll simply get the bug fixes without any changes needed. However, as a best practice, I'd recommend:

• Running your existing tests to verify everything works as expected
• Checking if your drag-and-drop functionality behaves correctly after the update

The bug fixes, particularly around handling files with empty types during drag events, should actually improve the reliability of your dropzone implementation.