-
-
Notifications
You must be signed in to change notification settings - Fork 961
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Riverpod 3.0 #3058
base: master
Are you sure you want to change the base?
Riverpod 3.0 #3058
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #3058 +/- ##
==========================================
- Coverage 95.76% 94.35% -1.41%
==========================================
Files 53 43 -10
Lines 2312 2339 +27
==========================================
- Hits 2214 2207 -7
- Misses 98 132 +34
|
Sync dev with master
@rrousselGit , Please give version 3.0.0, a release. |
Sync dev with master
fixes #3490
## Related Issues fixes #3853 <!-- Update to link the issue that is going to be fixed by this. Unless this concerns documentation, make sure to create an issue first before raising a PR. You do not need to describe what this PR is doing, as this should already be covered by the associated issue. If the linked issue isn't enough, then chances are a new issue is needed. Don't hesitate to create many issues! This can avoid working on something, only to have your PR closed or have to be rewritten due to a disagreement/misunderstanding. --> ## Checklist Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes (`[x]`). - [x] I have updated the `CHANGELOG.md` of the relevant packages. Changelog files must be edited under the form: ```md ## Unreleased fix/major/minor - Description of your change. (thanks to @yourgithubid) ``` - [x] If this contains new features or behavior changes, I have updated the documentation to match those changes.
@rrousselGit Noticed this has been a thing for over a year now- and also that there are new commits to dev; however, the prerelease hasn't even been updated/published in over a year. If not deploying 3.0, is there anything preventing a deploy of an updated prerelease? |
For real this time