Thanks for opening this issue!

• 🎉 We are excited about your ideas for improvement!

According to the information here, http 1.2.0 requires Dart 3.2 and which I believe means it could be used today. The latest version is 1.2.2 but requires Dart 3.3.

For more clarity...

It appears that the dependency has been already updated in the latest parse_server_sdk. However, parse_server_sdk_flutter still depends on an older 6.4.0 version of parse_server_sdk which requires http ^0.13.5.

"Because parse_server_sdk_flutter >=8.0.0 depends on parse_server_sdk ^6.4.0 which depends on http ^0.13.5, parse_server_sdk_flutter >=8.0.0 requires http ^0.13.5."

Searching further is appears that parse_server_sdk moved from http ^0.13.5 to ^1.1.0 with version 7.0.0.

So the real request is to update the parse_server_sdk dependency from ^6.4.0 to ^7.0.0.

I had similar experience. I tried to convince the team to upgrade dependencies regularly to keep up with other packages but it has LTS release cycle causing dependencies issues. Previous discussion: #1000. To overcome these issue I had to fork the repo and update dependencies regularly. Here is the repo: https://github.com/2shrestha22/Parse-SDK-Flutter/. You can checkout to develop branch for latest updates. Flutter community really needs a regularly updated repo.

We have a pinned issue with #968 if anyone wants to make a case for why we should change our support policy. We're open to suggestions, and please read through the discussion there so far to understand which arguments lead to the current support policy, in order to address these arguments.

This discussion got larger than I would have anticipated when I opened the issue. I guess at a fundamental level I don't understand why there are two packages maintained in the same Git repository and maintained by the same people, yet one package has a hard dependency on an outdated version of the other package. I'd get it if it were a dependency on package maintained outside of the developers' control. But the fact that parse_server_sdk_flutter MUST use an old version of parse_server_sdk just makes zero sense to me. Shouldn't releases of the two packages be coordinated as closely as possible?

Just my 2 cents... obviously there is something larger at play here that I don't understand yet.

One of them is a pure dart package and another in with flutter dependency. Dart package can be used without flutter.

One of them is a pure dart package and another in with flutter dependency. Dart package can be used without flutter.

Oh I get that part. I just assumed there would be better coordination between releases.