[dependabot]

Bumps the dependencies group with 5 updates in the / directory:

Package	From	To
crypto	3.0.7	3.0.8
fl_chart	1.2.0	1.3.0
flutter_midi_command	1.3.0	1.4.0
flutter_midi_command_ble	1.3.0	1.4.0
kiri_check	1.3.1	1.4.0

Updates crypto from 3.0.7 to 3.0.8

Release notes

Sourced from crypto's releases.

package:crypto v3.0.8

• Fix the sink returned by Hmac.startChunkedConversion not emitting a digest when addSlice is called with isLast: true.

• Drop unused pkg:typed_data dependency.

• Work-around dart-lang/sdk#63747.

• Speedup hashing 4 KiB inputs relative to version 3.0.7:

  Hash	AOT	dart2js	dart2wasm
  md5	1.2x	6.2x	1.4x
  sha224/sha256	1.35x	1.15x	1.05x
  sha384/sha512	3.1x	6.0x	5.1x

Commits

• 6903c6c [crypto] Prepare to publish 3.0.8 (#1026)
• f01024f [collection] Share Iterable and Set tests across wrapper_test.dart (#1028)
• c782eab Update convert package README and add examples (#999)
• 04da676 Remove dart:mirrors from package:collection test/wrapper_test.dart (#1027)
• f0d9935 [crypto] Don't end comment lines with a URL followed by a period (#1025)
• 5283f88 [crypto] Fix Hmac sink addSlice with isLast not emitting the digest (#1021)
• f5c8490 [crypto] Rotate the working variables in the SHA-256 compression loop (#1023)
• 3e29ec0 [crypto] Speed up the 64-bit SHA-512 sinks on the VM (#1022)
• 2c1dd6d [crypto] Add NIST SHA-384/512 and SHA-1 Monte vectors and chunked conversion ...
• 6f61929 [crypto] Add prefer-inline pragmas to the 32-bit SHA-512 helpers (#1019)
• Additional commits viewable in compare view

Updates fl_chart from 1.2.0 to 1.3.0

Release notes

Sourced from fl_chart's releases.

1.3.0

• FEATURE (by @​glemartret) Add the Gauge Chart (GaugeChart), #1933
• FEATURE (by @​imaNNeo) Add the gauge marker painter to draw markers on the Gauge Chart, #2096
• FEATURE (by @​jay-k98) Add stacked segment support for PieChartSectionData, #2004
• FEATURE (by @​enwi) Recognize secondary button pointer events (for example a mouse right-click) in the touch system, #1989
• PERFORMANCE (by @​PvtPuddles) Improve the performance of calculating touched spots in LineChart, #2101
• BUGFIX (by @​moriokaso) Prevent RangeError in badgeWidgetPaint when the number of pie sections increases, #2077
• BUGFIX (by @​Enurian) Fix axis labels disappearing due to an incorrect padding calculation in title filtering, #2080
• BUGFIX (by @​martin-dehlan) Clip only the enabled FlClipData sides in LineChart, #2107
• BUGFIX (by @​martin-dehlan) Clip only the enabled FlClipData sides in ScatterChart and CandlestickChart, #2108
• BUGFIX (by @​a1573595) Dispose gesture recognizers in RenderBaseChart, #2114
• BUGFIX (by @​a1573595) Keep axis title values on the interval grid for large values, #2112
• BUGFIX (by @​a1573595) Respect the axis range when formatting K/M/B axis labels. Default labels now also strip trailing zeros, #2113
• BUGFIX (by @​a1573595) Add localPosition to FlPanEndEvent so panEnd gets a touch response, #2111
• BUGFIX (by @​ultramcu) Detect touches on downward (negative) BarChartRodStackItems, #2103
• BUGFIX (by @​ultramcu) Avoid RangeError when toDashedPath receives an empty dashArray, #2105
• BUGFIX (by @​KuroGeo) Keep bar touch bounds independent of background rods, #2130
• BUGFIX (by @​SulimanAbdulrazzaq) Apply mouseCursorResolver even when touchCallback is not set, #2124
• BUGFIX (by @​omid-io) Prevent LateInitializationError in LineChart when a LineChartBarData has only null spots, #2115, #2119
• IMPROVEMENT (by @​Crucialjun) Refactor chart classes to use Equatable instead of EquatableMixin, #2120
• IMPROVEMENT (by @​imaNNeo) Loosen the equatable dependency constraint to >=2.1.0 <4.0.0

Changelog

Sourced from fl_chart's changelog.

1.3.0

• FEATURE (by @​glemartret) Add the Gauge Chart (GaugeChart), #1933
• FEATURE (by @​imaNNeo) Add the gauge marker painter to draw markers on the Gauge Chart, #2096
• FEATURE (by @​jay-k98) Add stacked segment support for PieChartSectionData, #2004
• FEATURE (by @​enwi) Recognize secondary button pointer events (for example a mouse right-click) in the touch system, #1989
• PERFORMANCE (by @​PvtPuddles) Improve the performance of calculating touched spots in LineChart, #2101
• BUGFIX (by @​moriokaso) Prevent RangeError in badgeWidgetPaint when the number of pie sections increases, #2077
• BUGFIX (by @​Enurian) Fix axis labels disappearing due to an incorrect padding calculation in title filtering, #2080
• BUGFIX (by @​martin-dehlan) Clip only the enabled FlClipData sides in LineChart, #2107
• BUGFIX (by @​martin-dehlan) Clip only the enabled FlClipData sides in ScatterChart and CandlestickChart, #2108
• BUGFIX (by @​a1573595) Dispose gesture recognizers in RenderBaseChart, #2114
• BUGFIX (by @​a1573595) Keep axis title values on the interval grid for large values, #2112
• BUGFIX (by @​a1573595) Respect the axis range when formatting K/M/B axis labels. Default labels now also strip trailing zeros, #2113
• BUGFIX (by @​a1573595) Add localPosition to FlPanEndEvent so panEnd gets a touch response, #2111
• BUGFIX (by @​ultramcu) Detect touches on downward (negative) BarChartRodStackItems, #2103
• BUGFIX (by @​ultramcu) Avoid RangeError when toDashedPath receives an empty dashArray, #2105
• BUGFIX (by @​KuroGeo) Keep bar touch bounds independent of background rods, #2130
• BUGFIX (by @​SulimanAbdulrazzaq) Apply mouseCursorResolver even when touchCallback is not set, #2124
• BUGFIX (by @​omid-io) Prevent LateInitializationError in LineChart when a LineChartBarData has only null spots, #2115, #2119
• IMPROVEMENT (by @​Crucialjun) Refactor chart classes to use Equatable instead of EquatableMixin, #2120
• IMPROVEMENT (by @​imaNNeo) Loosen the equatable dependency constraint to >=2.1.0 <4.0.0

Commits

• fc6a4b6 chore: Bump version to 1.3.0
• a64f0e7 fix(line_chart): Prevent LateInitializationError on barData with only null sp...
• 5a1e6af fix: Respect axis range when formatting K/M/B axis labels (#2113)
• c68593b fix: Keep axis title values on the interval grid for large values (#2112)
• 8912c3d fix: Add localPosition to FlPanEndEvent so panEnd gets a touch response (#2111)
• 3be2b1a fix: Avoid RangeError when toDashedPath receives an empty dashArray (#2105)
• 426caf1 fix: Detect touches on downward (negative) BarChartRodStackItems (#2103)
• 24814fc fix: Apply mouseCursorResolver even when touchCallback is not set (#2124)
• 18c712c fix: Keep bar touch bounds independent of background rods (#2130)
• 664baad docs: Fix touch handling sample types (#2131)
• Additional commits viewable in compare view

Updates flutter_midi_command from 1.3.0 to 1.4.0

Changelog

Sourced from flutter_midi_command's changelog.

1.4.0

• FIX: the declared SDK floor now states the truth: sdk >=3.12.0, flutter >=3.44.0. flutter_midi_command_android has required Flutter 3.44 since 1.3.0 — it builds with AGP 9 and Flutter's built-in Kotlin — and it is a hard dependency on every platform, so the >=3.24.0 this package advertised at 1.3.0 was never actually installable. Nothing changes for anyone already on Flutter 3.44 or newer; below it, pub resolves to 1.3.0 exactly as it already did.
• This package's own MIDI code is unchanged. The functional work in this release is in flutter_midi_command_ble 1.4.0 — advertised-service discovery filtering, pair-on-demand, and aging of peripherals that have stopped advertising. BLE is an opt-in transport, so upgrade that package to receive it and see its changelog for details.
• Update federated package constraints to ^1.4.0.

Commits

• 64f1a9e chore(release): correct the 1.4.0 release prep
• e1de1f5 chore(release): publish packages
• 70a255f Merge pull request #189 from InvisibleWrench/fix/ble-connect-backoff
• fb21546 Merge pull request #188 from InvisibleWrench/fix/ble-scan-aging
• c2fb724 Merge pull request #187 from InvisibleWrench/fix/ble-sysex-terminator-diagnostic
• 63066e0 fix(ble): retry a refused connect on a growing delay
• 981b303 feat(ble): report incoming framing this transport cannot use
• 94d635a test(ble): stop the aging sweep test depending on scheduling
• 2d6c8e5 feat(ble): drop peripherals that have stopped advertising
• fe7a75c Merge pull request #186 from InvisibleWrench/fix/ble-pair-on-demand
• Additional commits viewable in compare view

Updates flutter_midi_command_ble from 1.3.0 to 1.4.0

Changelog

Sourced from flutter_midi_command_ble's changelog.

1.4.0

• FIX: the declared SDK floor now states the truth: sdk >=3.12.0, flutter >=3.44.0. flutter_midi_command_android has required Flutter 3.44 since 1.3.0 — it builds with AGP 9 and Flutter's built-in Kotlin — and it is a hard dependency on every platform, so the >=3.24.0 this package advertised at 1.3.0 was never actually installable. Nothing changes for anyone already on Flutter 3.44 or newer; below it, pub resolves to 1.3.0 exactly as it already did.
• This package's own MIDI code is unchanged. The functional work in this release is in flutter_midi_command_ble 1.4.0 — advertised-service discovery filtering, pair-on-demand, and aging of peripherals that have stopped advertising. BLE is an opt-in transport, so upgrade that package to receive it and see its changelog for details.
• Update federated package constraints to ^1.4.0.

Commits

• 64f1a9e chore(release): correct the 1.4.0 release prep
• e1de1f5 chore(release): publish packages
• 70a255f Merge pull request #189 from InvisibleWrench/fix/ble-connect-backoff
• fb21546 Merge pull request #188 from InvisibleWrench/fix/ble-scan-aging
• 63066e0 fix(ble): retry a refused connect on a growing delay
• 981b303 feat(ble): report incoming framing this transport cannot use
• 94d635a test(ble): stop the aging sweep test depending on scheduling
• 2d6c8e5 feat(ble): drop peripherals that have stopped advertising
• f981d6a docs(ble): describe the failure modes without naming a device
• f4439d6 Merge #185 (advertised-MIDI-service scan gate) into pair-on-demand
• Additional commits viewable in compare view

Updates kiri_check from 1.3.1 to 1.4.0

Release notes

Sourced from kiri_check's releases.

1.4.0

This release fixes many faults in how failing examples are shrunk and reported, in both stateless properties and stateful tests. Counterexamples are now smaller and correct, and the report keeps the original failure. See #32 for the details.

Breaking change: StatefulFalsifyingExample.exception is now Object? instead of Exception?, so that it can hold an Error. Only code that assigns it to an Exception-typed variable needs a change.

Highlights:

• Properties failing with an Error (a RangeError, a StateError, a failed assert and so on) are now shrunk like ones failing with an Exception.

• Stateful shrinking no longer reports sequences that break preconditions, and now actually shrinks values.

• Async properties are now shrunk correctly, and setUp/tearDown run for each shrunk example.

• The failure report shows the original example alongside the shrunk one:

  Falsifying example: 10 (seed 20261008)
  Original example: 736
  

• The new windows option of uri generates file URIs from Windows paths, and file URIs are now the same on every platform.

Thanks to the user who reported these faults with detailed reproductions! 🎉

Full Changelog: v1.3.2...v1.4.0

Changes

• [CHANGE] Breaking: StatefulFalsifyingExample.exception is now Object? instead of Exception?, so that it can hold an Error
• [ADD] Add the windows option to uri to generate file URIs from Windows paths such as C:\dir\file
• [ADD] Show the original falsifying example (or sequence in stateful tests) alongside the shrunk one in the failure report
• [FIX] uri now generates the same file URIs on every platform; on Windows it threw "Illegal character in path"
• [FIX] A property failing with an Error (a RangeError, a StateError, a failed assert, a StackOverflowError and so on) is now shrunk like one failing with an Exception, and its tear-down callbacks run. An OutOfMemoryError is rethrown without shrinking
• [FIX] In stateful tests, a command now runs with the value its precondition was checked with during generation, instead of a value generated again, which could fail the precondition and the property
• [FIX] StatefulFalsifyingExample.originalSteps now holds the values of the original failure, not the values changed by shrinking
• [FIX] Stateful shrinking no longer counts a step whose precondition is not satisfied as a failure, which reported sequences that could never fail. Such a step is dropped from the candidate sequence
• [FIX] Stateful shrinking now shrinks the value of one step at a time, from the smallest failing value, so values are actually made smaller
• [FIX] Stateful shrinking can now drop a single step from the middle of a sequence
• [FIX] The stateful failure report keeps the exception of the original failure when no smaller failing sequence is found
• [FIX] Stateful shrinking calls Behavior.setUp and Behavior.tearDown exactly once for each run
• [FIX] An async property block is now awaited while shrinking, so its failures are shrunk instead of being reported unshrunk with a separate error for each shrunk example
• [FIX] setUp, tearDown and the forAll callbacks are now called for each shrunk example, as for each generated example
• [FIX] onGenerate and onShrink callbacks returning a Future are now awaited
• [FIX] Correct the documentation of onFalsify in forAll: it is called after shrinking, with the shrunk example

1.3.2

This is a maintenance release that updates dependencies. There are no changes to the public API or behavior of the library.

The timezone dependency has been updated to ^0.11.0, so kiri-check now works with the latest timezone releases. Development dependencies (lints, very_good_analysis) have also been updated.

Thanks to @​0rzech for the timezone update in #30! 🎉

Full Changelog: v1.3.1...v1.3.2

... (truncated)

Changelog

Sourced from kiri_check's changelog.

1.4.0

• [CHANGE] Breaking: StatefulFalsifyingExample.exception is now Object? instead of Exception?, so that it can hold an Error
• [ADD] Add the windows option to uri to generate file URIs from Windows paths such as C:\dir\file
• [ADD] Show the original falsifying example (or sequence in stateful tests) alongside the shrunk one in the failure report
• [FIX] uri now generates the same file URIs on every platform; on Windows it threw "Illegal character in path"
• [FIX] A property failing with an Error (a RangeError, a StateError, a failed assert, a StackOverflowError and so on) is now shrunk like one failing with an Exception, and its tear-down callbacks run. An OutOfMemoryError is rethrown without shrinking
• [FIX] In stateful tests, a command now runs with the value its precondition was checked with during generation, instead of a value generated again, which could fail the precondition and the property
• [FIX] StatefulFalsifyingExample.originalSteps now holds the values of the original failure, not the values changed by shrinking
• [FIX] Stateful shrinking no longer counts a step whose precondition is not satisfied as a failure, which reported sequences that could never fail. Such a step is dropped from the candidate sequence
• [FIX] Stateful shrinking now shrinks the value of one step at a time, from the smallest failing value, so values are actually made smaller
• [FIX] Stateful shrinking can now drop a single step from the middle of a sequence
• [FIX] The stateful failure report keeps the exception of the original failure when no smaller failing sequence is found
• [FIX] Stateful shrinking calls Behavior.setUp and Behavior.tearDown exactly once for each run
• [FIX] An async property block is now awaited while shrinking, so its failures are shrunk instead of being reported unshrunk with a separate error for each shrunk example
• [FIX] setUp, tearDown and the forAll callbacks are now called for each shrunk example, as for each generated example
• [FIX] onGenerate and onShrink callbacks returning a Future are now awaited
• [FIX] Correct the documentation of onFalsify in forAll: it is called after shrinking, with the shrunk example

1.3.2

• [CHANGE] Update timezone dependency to ^0.11.0 (@​0rzech, #30)
• [CHANGE] Update dev dependencies (lints, very_good_analysis)

Commits

• 19b4953 Merge branch 'release/v1.4.0'
• 6f09762 release: v1.4.0
• 896f60a Merge branch 'fix/shrinking-and-reporting' into develop
• 54d2e17 feat(uri): Add windows option and generate the same file URIs everywhere
• 888852d chore(ci): Run tests on Windows and for fix branches
• 214fc57 fix(stateful): Run commands with the values checked by preconditions
• e5d1fad fix: Shrink properties failing with an Error
• 58ccdc7 fix(property): Await async blocks and run setUp/tearDown while shrinking
• d76d8b3 fix(stateful): Shrink sequences without breaking preconditions
• bcfc52f test: Add tests reproducing faults in shrinking and failure reports
• 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 <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions