Help : Update plugins with latest commit #124
Comments
|
need it too, please update packages |
|
Up! |
|
This package is now community supported. If you would like to contribute please comment and we can get you either as a maintainer or owner of the Flutter SDK. |
Add me as a maintainer |
@zdavis-rollbar Can you please elaborate on this? I'm not seeing any announcement or note in the docs about this. To me this sounds like Rollbar is effectively abandoning the project... After the recent xz backdoor fiasco I'm not feeling super enthused about Rollbar handing out maintainership of this package so easily... |
|
We have included a statement in the readme file: Attention: As of April 2024, Rollbar will not be actively updating this repository and plans to archive it. We encourage our community to fork this repo if you wish to continue its development. While Rollbar will no longer be engaging in active development, we remain committed to reviewing and merging pull requests, particularly those about security updates. If an actively maintained fork emerges, please let us know, and we will gladly link to it from our documentation. |
|
@zdavis-rollbar Thanks for adding that to the readme. Bit of a nitpick, but these two statements seem to contradict each other:
(can't review/merge pull requests if the repo is archived). I understand that everyone's trying to cut costs, but I'm a little perplexed by this decision from Rollbar. Flutter is the most popular cross-platform mobile SDK (161k stars on Github, compared to 115k stars for React Native). I hope management at Rollbar will reconsider pulling the plug on the project. How is the community supposed to triage something like #128, for example? That seems like something that would be much easier to troubleshoot and fix if you had visibility into the Rollbar backend, which the community obviously doesn't have. |
Since Rollbar will no longer be publishing package updates to pub.dev, it
will be helpful for many users to "vendor" the Rollbar packages into their
projects so that they can have full control over package versions, pull in
fixes from the community, etc. For example, the rollbar_dart package on
pub.dev currently has an old http dependency, even though this has already
been updated on the main branch.
Add instructions to the README for vendoring rollbar_flutter into a user
project, and change the internal rollbar_{dart,flutter} dependencies to be
"path" dependencies (pulling from within this repo) rather than
"hosted" (pulling from pub.dev).
Fixes rollbar#124
Can you please either update the flutter website with lates commit (Which is bumping http version ) or at least fix the dependency of
roll_bar_fluttto depend onrollbar_dart1.3.1 instade of 1.3.0The text was updated successfully, but these errors were encountered: