Skip to content

Conversation

@vincenzopalazzo
Copy link
Collaborator

graphql 5.2.4:

  • fix: upgrade normalize dependency to be 0.10.0 compatible

graphql_flutter 5.3.0 (minor bump due to dependency changes):

  • BREAKING: switched from hive to hive_ce - users importing package:hive/hive.dart directly should switch to package:hive_ce/hive_ce.dart
  • chore: update connectivity_plus from ^6.1.3 to ^7.0.0
  • fix: update flutter_hooks constraint to <0.22.0

🤖 Generated with Claude Code

There are some simple steps to get your PR merged, that are the following:

  • Describe your PR and why a maintainer should merge it;
  • Put the same description inside the commit body otherwise if we change github hosting you application will be based on a instable source code;
  • Write the commit header in the way that it is following these simple rules [1]
  • Make sure that your PR will pass the CI
  • Wait for an review 😄 that will not happen if one of the previous step is missing.

1

Fixes #1506

graphql 5.2.4:
- fix: upgrade normalize dependency to be 0.10.0 compatible

graphql_flutter 5.3.0 (minor bump due to dependency changes):
- BREAKING: switched from `hive` to `hive_ce` - users importing
  `package:hive/hive.dart` directly should switch to `package:hive_ce/hive_ce.dart`
- chore: update connectivity_plus from ^6.1.3 to ^7.0.0
- fix: update flutter_hooks constraint to <0.22.0

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR bumps package versions for graphql to 5.2.4 and graphql_flutter to 5.3.0. The graphql package receives a patch update to fix a dependency compatibility issue with the normalize package. The graphql_flutter package receives a minor version bump due to breaking changes (migration from hive to hive_ce) and dependency updates for connectivity_plus and flutter_hooks.

Key changes:

  • Updated graphql package from 5.2.3 to 5.2.4
  • Updated graphql_flutter package from 5.2.1 to 5.3.0
  • Updated graphql_flutter dependency on graphql to ^5.2.4

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.

File Description
packages/graphql_flutter/pubspec.yaml Bumped version to 5.3.0 and updated graphql dependency to ^5.2.4
packages/graphql_flutter/changelog.json Updated version metadata to v5.3.0
packages/graphql/pubspec.yaml Bumped version to 5.2.4
packages/graphql/changelog.json Updated version metadata to v5.2.4

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

- actions/checkout@v2 → @v4
- subosito/flutter-action@v1 → @v2

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
@codecov
Copy link

codecov bot commented Dec 4, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 63.19%. Comparing base (63076ed) to head (eab731d).
⚠️ Report is 50 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1511      +/-   ##
==========================================
- Coverage   66.64%   63.19%   -3.45%     
==========================================
  Files          28       41      +13     
  Lines        1487     1864     +377     
==========================================
+ Hits          991     1178     +187     
- Misses        496      686     +190     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Please do not introduce breaking changes without bumping major version

2 participants