deps:(deps): bump awesome_notifications from 0.12.0 to 0.12.1

[dependabot]

Bumps awesome_notifications from 0.12.0 to 0.12.1.

Changelog

Sourced from awesome_notifications's changelog.

[0.12.1] - 2026-07-01

Changed

• Critical alerts are now a channel-only capability, with the same rule on iOS and Android. A notification is delivered as a critical alert only when its channel is registered as critical (NotificationChannel(criticalAlerts: true)). This mirrors Android, where Do-Not-Disturb bypass is inherently a channel property with no per-notification override, giving one predictable cross-platform behavior.

Fixed

• iOS: the critical-alert availability check no longer blocks the notification build. The entitlement/permission is resolved asynchronously and read from cache during the build, so the result is always correct — including inside notification service extensions — without stalling delivery.
• Android: critical alerts no longer override the device's global Do-Not-Disturb settings. The global setInterruptionFilter/setNotificationPolicy override was removed; critical delivery relies solely on the per-channel setBypassDnd, which is app-scoped and respects the user's system-wide choices.
• iOS: getInitialNotificationAction() no longer hangs — or drops the launch action — under the UIScene lifecycle. The notification-center delegate is now claimed at plugin registration and the launch state is settled on activation, so an app launched by tapping a notification captures its initial action under both the classic and UIScene lifecycles.

Breaking changes

• NotificationContent.criticalAlert was removed. Critical alerts are configured on the channel instead: register a NotificationChannel(criticalAlerts: true) and post notifications to it. A criticalAlert key still present in a content payload is ignored.

Dependencies

• Requires IosAwnCore and AndroidAwnCore 0.12.1.

Commits

• See full diff 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)