dart pub upgrade --major-versions --tighten

[sensuikan1973]

Auto-generated by create-pull-request

---

See: https://github.com/peter-evans/create-pull-request/blob/master/docs/concepts-guidelines.md#triggering-further-workflow-runs

[gemini-code-assist]

Hello @sensuikan1973, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

Summary of Changes

Hello team, gemini-code-assist here to provide a summary of this pull request. This PR appears to be an automated update of the project's dependencies, executed using the command dart pub upgrade --major-versions --tighten. The changes primarily involve bumping version numbers for several packages in both the main pubspec.yaml and example/pubspec.yaml files, and subsequently updating the corresponding pubspec.lock files. Additionally, there's a notable change in the generated FFI bindings file, likely a side effect of one of the dependency upgrades.

Highlights

• Automated Dependency Upgrade: This pull request was automatically generated to upgrade project dependencies using dart pub upgrade --major-versions --tighten.
• Package Version Bumps: Several development dependencies have been updated, including pedantic_sensuikan1973 and test, in both the main package and the example project.
• FFI Bindings Update: The generated FFI bindings file (lib/src/ffi/bindings.dart) has been modified, likely due to changes in a dependency like ffigen or the underlying C headers, involving renaming of symbols related to timezone.

Changelog

Click here to see the changelog

• example/pubspec.lock
  • Updated pedantic_sensuikan1973 from 5.12.0 to 5.13.0.
  • Updated the local package dependency version from 7.44.0 to 7.45.0.
• example/pubspec.yaml
  • Updated the version constraint for pedantic_sensuikan1973 from ^5.12.0 to ^5.13.0.
• lib/src/ffi/bindings.dart
  • Renamed the internal FFI pointer _timezone to _timezone$1.
  • Renamed the timezone getter and setter to timezone$1.
  • Renamed the FFI struct timezone$1 to timezone.
• pubspec.lock
  • Updated pedantic_sensuikan1973 from 5.12.0 to 5.13.0.
  • Updated test from 1.26.1 to 1.26.2.
  • Updated test_core from 0.6.10 to 0.6.11.
  • Updated vm_service from 15.0.0 to 15.0.1.
• pubspec.yaml
  • Updated the version constraint for pedantic_sensuikan1973 from ^5.12.0 to ^5.13.0.
  • Updated the version constraint for test from ^1.26.1 to ^1.26.2.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in issue comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

---

Dependencies rise,
pub upgrade brings new versions,
Hope tests still pass now.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.41%. Comparing base (4c478ef) to head (dac584a).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #771   +/-   ##
=======================================
  Coverage   96.41%   96.41%           
=======================================
  Files          15       15           
  Lines         669      669           
=======================================
  Hits          645      645           
  Misses         24       24           

Flag	Coverage Δ
macos-latest	96.26% <ø> (ø)
ubuntu-latest	96.11% <ø> (ø)
unit_test	96.41% <ø> (ø)
windows-latest	96.41% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[gemini-code-assist]

Code Review

This pull request primarily involves upgrading dependencies, as indicated by the title dart pub upgrade --major-versions --tighten. The changes include updates to pubspec.yaml and pubspec.lock files for both the main package and the example.

Additionally, there's a renaming adjustment within the FFI bindings (lib/src/ffi/bindings.dart). Specifically, the accessor for the C global variable timezone has been renamed to timezone$1, and the Dart class representing the C struct timezone has been renamed from timezone$1 to timezone. This appears to be a standard way to resolve name collisions in FFI-generated code, likely triggered by updates to ffigen, analyzer, or linting rules from pedantic_sensuikan1973.

Overall, the changes seem to be in order and are typical for automated dependency management. The FFI binding change is internal to LibEdaxBindings and, assuming this class is not part of the stable public API (due to its location in lib/src/), these changes should not be breaking for users of the package.

Summary of Findings

• Dependency Upgrades: Several dependencies in pubspec.yaml and pubspec.lock files have been upgraded (e.g., pedantic_sensuikan1973, test, and transitive dependencies like analyzer, vm_service, test_core). This is generally good for keeping the package up-to-date with the ecosystem.
• FFI Binding Renaming: The FFI bindings in lib/src/ffi/bindings.dart have renamed the accessors for the C global variable timezone to timezone$1 and the Dart class for the C struct timezone from timezone$1 to timezone. This is a common strategy to resolve name collisions in FFI code. Given that lib/src/ffi/bindings.dart is typically considered internal (as per Dart's lib/src convention) and the LibEdax class does not seem to expose these members directly, this change is likely non-breaking for the public API of the package. This was not commented on with a specific code review comment due to the configured severity threshold for comments.

Merge Readiness

The pull request appears to be in good shape for merging, primarily consisting of automated dependency upgrades and a consequential internal adjustment to FFI bindings. Assuming CI tests pass, these changes should be safe. As an AI reviewer, I am not authorized to approve pull requests; please ensure appropriate human review and approval before merging.