Bump tray_manager from 0.5.3 to 0.7.0

[dependabot]

Bumps tray_manager from 0.5.3 to 0.7.0.

Release notes

Sourced from tray_manager's releases.

v0.7.0

tray_manager is now built on nativeapi: the per-platform plugin code is gone, and one C++ core drives macOS, Windows and Linux.

• Breaking: package:tray_manager/tray_manager.dart exports the native API — TrayIcon, Menu, MenuItem, Image and their events. Several tray icons at once, double-click events, contextMenuTrigger, menu item icons, radio groups and accelerators come with it.
• The 0.5.x API moved to package:tray_manager/legacy.dart: trayManager, TrayListener, and a Menu / MenuItem pair with the menu_base shape (menu_base itself is no longer a dependency). Existing apps change one import. It is a bridge: everything in it is @Deprecated and will be removed in a later release. The README lists the behaviour differences and maps each old call to the native API.
• Breaking: requires Flutter 3.47 / Dart 3.13 and macOS 10.15, and depends on nativeapi ^0.3.0. CI builds and the publish workflow pin Flutter 3.47.5.
• Linux: the tray icon is a StatusNotifierItem, and setToolTip works. Tray icon clicks are not reported there — the panel keeps them and opens the menu itself, as it did in 0.5.x. Builds need GTK 3, X11 and Xi development files; libayatana-appindicator3-dev is not one of them (nativeapi 0.3.0 stopped requiring and linking it).
• Windows: .png icons work as well as .ico.
• MenuItem.label, toolTip, checked and disabled of the legacy API update the visible menu when assigned; onClick runs once per click, with or without a TrayListener. A native checkbox item is not toggled by a click.
• New example on package:flutter/widgets.dart alone; the full one is nativeapi's tray_icon_example.

Upgrading from 0.5.x

Change one import and existing code keeps working: package:tray_manager/legacy.dart carries the 0.5.x API (trayManager, TrayListener, and a Menu / MenuItem pair with the menu_base shape, without depending on menu_base). Everything in it is deprecated and goes away in a later release; the README maps each old call to its native counterpart.

On Linux, one behaviour differs and will not come back: tray icon clicks are not reported — the panel keeps them and opens the menu itself.

📦 https://pub.dev/packages/tray_manager/versions/0.7.0

Full Changelog: leanflutter/tray_manager@v0.5.3...v0.7.0

Changelog

Sourced from tray_manager's changelog.

0.7.0

tray_manager is now built on nativeapi: the per-platform plugin code is gone, and one C++ core drives macOS, Windows and Linux.

• Breaking: package:tray_manager/tray_manager.dart exports the native API — TrayIcon, Menu, MenuItem, Image and their events. Several tray icons at once, double-click events, contextMenuTrigger, menu item icons, radio groups and accelerators come with it.
• The 0.5.x API moved to package:tray_manager/legacy.dart: trayManager, TrayListener, and a Menu / MenuItem pair with the menu_base shape (menu_base itself is no longer a dependency). Existing apps change one import. It is a bridge: everything in it is @Deprecated and will be removed in a later release. The README lists the behaviour differences and maps each old call to the native API.
• Breaking: requires Flutter 3.47 / Dart 3.13 and macOS 10.15, and depends on nativeapi ^0.3.0. CI builds and the publish workflow pin Flutter 3.47.5.
• Linux: the tray icon is a StatusNotifierItem, and setToolTip works. Tray icon clicks are not reported there — the panel keeps them and opens the menu itself, as it did in 0.5.x. Builds need GTK 3, X11 and Xi development files; libayatana-appindicator3-dev is not one of them (nativeapi 0.3.0 stopped requiring and linking it).
• Windows: .png icons work as well as .ico.
• MenuItem.label, toolTip, checked and disabled of the legacy API update the visible menu when assigned; onClick runs once per click, with or without a TrayListener. A native checkbox item is not toggled by a click.
• New example on package:flutter/widgets.dart alone; the full one is nativeapi's tray_icon_example.

Commits

• de4d286 Depend on nativeapi 0.3.0; release 0.7.0
• 7b809e4 Require Flutter 3.47 / Dart 3.13 and pin CI to 3.47.5
• 37e1686 Correct the README and the 0.6.0 notes; 0.6.1
• 5b8e35b Remove visit count badge from READMEs
• 6ed6cf7 Linux builds still need libayatana-appindicator3-dev with nativeapi 0.2.7
• 796afa7 Make analysis pass on stable Flutter; let CI follow the latest stable
• 1f16a7d Depend on nativeapi ^0.2.7
• 2687052 Prepare 0.6.0
• 440db46 Merge main (0.5.3) into dev, keeping dev
• 7e3d7b4 Rebuild the example around the 0.5.x compatible API
• 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)

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.