feat: upgraded connectivity_plus package

[Avinash-dhiraj]

• As app store introduced mandatory privacy manifest files for some of packages being used in the application. connectivity_plus 6.0.2 is one of them and current version of connectivity_plus 6.0.2 has added support for privacy manifest but graphql_flutter still using connectivity_plus 5.0.0 which leads into compatibility issue. App store is very specific about the deadline of these as well which is 1st of may.;

upgraded connectivity_plus from 5.0.0 to 6.0.2

Please merge this on priority as this breaking changes is needed for all the flutter application which is using connectivity_plus 6.0.2 along with graphql_flutter

Fixes #1423 (comment)

[vincenzopalazzo]

looks like that needs a rebase, please ping me when the conflict are fixed

[Avinash-dhiraj]

looks like that needs a rebase, please ping me when the conflict are fixed

there is a conflict in pubspec file

<<<<<<< connectivity-plus-upgrade
  connectivity_plus: ^6.0.2
=======
  connectivity_plus: ^5.0.0
>>>>>>> main

<<<<<<< connectivity-plus-upgrade
  sdk: '>=3.3.0 <=4.0.0'
  flutter: ">=3.19.5"
=======
  sdk: '>=2.12.0 <4.0.0'
  flutter: ">=2.11.0"
>>>>>>> main

which can be resolved when someone merge it.

[vincenzopalazzo]

We do not use merge commit inside the PR, so you should rebase it with git rebase.

This commit can be removed dee9b94

In addition, I left a couple of comments because I am a little bit confused while looking at your commit history

I think just the first one is what we want to merge?

[johnmartel]

@vincenzopalazzo any chance of getting this merged and released quickly if I fork this PR and submit an updated version? This is creating an unnecessary roadblock for projects that use both graphql_flutter and connectivity_plus that want to upgrade their dependencies.

[selawik]

Any updates?

[SachinCodeMatrix]

@Avinash-dhiraj @vincenzopalazzo please check this

[vincenzopalazzo]

This is unresolved #1424 (review)

I have nothing to check

[vincenzopalazzo]

Closing because looks like that there is already a fix #1423 (comment)

Please open a new PR with a good git history if the problem persit