Parse-SDK-Flutter
Parse-SDK-Flutter copied to clipboard
fix: Add support for Dart `3.6`, `3.7`; remove support for Dart `3.2`, `3.3`, `3.4`, `3.5`, `3.3`
Pull Request
- Report security issues confidentially.
- Any contribution is under this license.
- Link this pull request to an issue.
Issue
Add support for Dart 3.6, 3.7; remove support for Dart 3.2, 3.3, 3.4, 3.5, 3.3
Closes: #1026
Approach
n/a
Tasks
- [ ] Add tests
- [ ] Add changes to documentation (guides, repository pages, code comments)
🚀 Thanks for opening this pull request!
Codecov Report
:white_check_mark: All modified and coverable lines are covered by tests.
:white_check_mark: Project coverage is 43.72%. Comparing base (c388545) to head (36eadaf).
:warning: Report is 13 commits behind head on master.
Additional details and impacted files
@@ Coverage Diff @@
## master #1040 +/- ##
==========================================
+ Coverage 43.37% 43.72% +0.35%
==========================================
Files 61 61
Lines 3463 3465 +2
==========================================
+ Hits 1502 1515 +13
+ Misses 1961 1950 -11
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
:rocket: New features to boost your workflow:
- :snowflake: Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
@mbfakourii just a friendly ping, so we can get this merged.
@mtrezza
Sorry for the delay, I was busy. I think an automated CI is needed for these changes. What do you think?
@mbfakourii What do you mean by automated CI?
@mbfakourii What do you mean by automated CI?
I mean, this PR that was created should be done automatically.
@mbfakourii The only thing we currently automate in other repos is the version increment and release publishing. So that you don't need to change the package version and write a change log entry manually anymore. Do you mean that?
It's been 5 weeks since last update. Hope this isn't getting lost in the crowd.
Closed with no commits? So support of Dart > 3.5 just goes out of plan?
@mbfakourii Was this PR ready for merge?