[dependabot]

Bumps malzariey/filament-daterangepicker-filter from 5.0.7 to 5.0.9.

Release notes

Sourced from malzariey/filament-daterangepicker-filter's releases.

5.0.9 — the picker stays on screen on phones

Fixed

• Mobile dropdown positioning at narrow widths — at 390 px the dropdown could open above the top of the viewport, leaving the presets unreachable, and a strip of calendar scrolled under the sticky Apply/Cancel bar. The dropdown now shifts on the cross axis to stay on screen, and the apply bar sits flush at the bottom. Desktop placement is unchanged.
• The input clears on unparseable state — when the filter state could not be parsed, the input kept showing the previous range (or the previous end date when only one end parsed). Parsing now starts from an empty selection.
• The calendar's "today" uses the display timezone — the today marker and keyboard focus used the browser clock; they now follow timezone(). The README's custom-preset example now uses $component->now() instead of app-timezone now().
• Presets highlight with timePicker() enabled — date-only presets were already selected as 00:00–23:59:59, but the active highlight and useRangeLabels() never matched them. One normaliser now drives select, highlight and label, and the label refreshes after a time edit.
• Arabic label typo — «آخر 7 أيام» and «آخر 30 يوم» were spelled «أخر», and «هذه السنة» was «هذة».

Also in this release

• Month and year pickers filter the whole month or year — 06/2026 was read as today's day of June, and on the 29th–31st 02/2026 rolled into March and dropped the filter. Month/year bounds now cover the whole period.

Merged pull requests

• #261 Fix mobile dropdown placement, stale input on bad state, and preset matching under timePicker

Upgrading

No action needed. Run php artisan filament:assets on deploy as usual, because the JS and CSS in dist/ changed.

5.0.8 — a half-picked range no longer 500s the table

Fixed — a half-picked date range answered 500 on every visit

When a DateRangeFilter's state held a single date — the user picked the start of a range but not the end — apply() exploded it into one element and passed the raw string to modifyQueryUsing as $startDate. Any closure typed ?CarbonInterface threw:

$startDate must be of type ?CarbonInterface, string given

Filament persists filter state per user, so that user then got a 500 on the table on every visit until their session expired. State that did not match the format threw InvalidFormatException the same way.

Now:

Filter state	5.0.7	5.0.8
27/10/2026 - 28/10/2026	both days	unchanged
27/10/2026 (lone date)	raw string to the callback → TypeError / 500	that whole day, start-of-day → end-of-day in the display timezone, converted to the storage timezone
not-a-date, 31/02/2026, wrong format	InvalidFormatException → 500	ignored: callback gets null, null, filter does nothing, no indicator chip

modifyQueryUsing now always receives Carbon instances or nulls. The input also shows a persisted lone date as that day instead of an empty box over an active filter. Covered by tests/SingleDateStateTest.php.

Also fixed

• Time picker end bound — without seconds in the format, the end "23:59" was read as 23:59:00 and dropped the last 59 seconds of every range, including the end of each built-in preset. It is now the end of that minute; formats with seconds keep the exact second.
• Time picker minute select — the default end is 23:59 but the default increment is 30, so the select showed 00 while :59 was applied. The selected minutes are now always offered.
• RTL / Arabic panels — the trigger input and the selection preview showed 23:59 27/10/2026 - 00:00 27/10/2026 for 27/10/2026 00:00 - 27/10/2026 23:59. Dates now read correctly; the preview arrow is mirrored.
• Setters that accepted what the getters could not handle: firstDayOfWeek(fn () => 6) on the filter (TypeError), autoApply(fn () => …) (TypeError), string startDate() / endDate() / defaultCustom() (format() on string), and CarbonImmutable presets (sent as UTC timestamps, so the previous day west of UTC).

Merged pull requests

... (truncated)

Commits

• b0c03d6 Merge pull request #261 from malzariey/fix/presets-state-mobile-bar
• 8864cd2 Fix Arabic preset labels: آخر (last) and هذه (this) were misspelled
• 99284a5 Fix mobile dropdown placement, stale input on bad state, and preset matching ...
• 2749375 Delete superseded tests the owner approved on 29 Oct
• c33cd77 Test DateRangeFilter through a real Filament table
• d303759 Run the test suites in GitHub Actions on every push and PR to x5
• 51775d0 Commit a phpunit.xml.dist so a fresh clone can run the suite
• 4f1a1c4 Filter whole months and years in the month and year pickers
• 9e45ae9 Add run-and-deploy header to CLAUDE.md and list known gaps
• ebc91dd Reject rolled-over dates; keep the default-date fallback in non-strict Carbon
• 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 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)