fix(core): Coerce BinaryDataConfig dbMaxFileSizeSchema to a number

[davidpanic]

Summary

This is a fix for issue #23919. The environment variable N8N_BINARY_DATA_DATABASE_MAX_FILE_SIZE now works correctly.

Related Linear tickets, Github issues, and Community forum posts

fixes #23919

Review / Merge checklist

• PR title and summary are descriptive. (conventions)
• Docs updated or follow-up ticket created.
• Tests included.
• PR Labeled with release/backport (if the PR is an urgent fix that needs to be backported)

[CLAassistant]

All committers have signed the CLA.

[cubic-dev-ai]

No issues found across 1 file

[n8n-assistant]

Hey @davidpanic,

Thank you for your contribution. We appreciate the time and effort you’ve taken to submit this pull request.

Before we can proceed, please ensure the following:
• Tests are included for any new functionality, logic changes or bug fixes.
• The PR aligns with our contribution guidelines.

Regarding new nodes:
We no longer accept new nodes directly into the core codebase. Instead, we encourage contributors to follow our Community Node Submission Guide to publish nodes independently.

If your node integrates with an AI service that you own or represent, please email nodes@n8n.io and we will be happy to discuss the best approach.

About review timelines:
This PR has been added to our internal tracker as "GHC-6189". While we plan to review it, we are currently unable to provide an exact timeframe. Our goal is to begin reviews within a month, but this may change depending on team priorities. We will reach out when the review begins.

Thank you again for contributing to n8n.

[ivov]

@davidpanic Thank you very much for spotting and fixing this. Added a few tests to prevent regressions.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[n8n-assistant]

Got released with n8n@2.4.0