search

PalisadoesFoundation / talawa

Community Organization Management Software. Click on the link below to see our documentation.
https://docs.talawa.io/
GNU General Public License v3.0
338 stars 465 forks source link

Bump flutter_local_notifications from 17.2.4 to 18.0.0 #2631

Closed dependabot[bot] closed 3 weeks ago

dependabot[bot] commented 3 weeks ago

Bumps flutter_local_notifications from 17.2.4 to 18.0.0.

Release notes

Sourced from flutter_local_notifications's releases.

flutter_local_notifications-v18.0.0

  • Breaking changes Bumped minimum Flutter SDK requirement to 3.13. Consequently the minimum OS requirements for each platform has been updated as well
    • [Android] minimum Android version is now 4.4 (API level 19)
    • [iOS] minimum iOS version is now 11
    • [macOS] minimum macOS version is now 10.14
  • [Android] Breaking change removed the deprecated androidAllowWhileIdle parameter from zonedSchedule() and periodicallyShow() methods. androidScheduleMode is now a required parameter
  • Breaking change plugin has been fixed with regards to how it registers the platform-specific implementations of the plugin. Thanks to the PR from Kate. Any written tests done on the [FlutterLocalNotificationsPlugin] will need to manually call the registerWith() method that has been added to each implementation. This affects the following platforms/classes where the registerWith() method was added
    • [Android] AndroidFlutterLocalNotificationsPlugin
    • [iOS] IOSFlutterLocalNotificationsPlugin
    • [macOS] MacOSFlutterLocalNotificationsPlugin
  • [iOS] Breaking change Removed onDidReceiveLocalNotification callback as this was only relevant on iOS versions older than 10
  • Fixed example app to have the appropriate permissions for foreground services
  • Updated readme when it comes to setting up the AndroidManifest.xml file to include details of what's needed for foreground services. Note these details were already available in the API docs

flutter_local_notifications-v18.0.0-dev.3

  • Included changes from 17.2.4 release that was done to add in a privacy manifest file to macOS implementation

flutter_local_notifications-v18.0.0-dev.2

  • [iOS] Breaking change Removed onDidReceiveLocalNotification callback as this was only relevant on iOS versions older than 10

flutter_local_notifications-v18.0.0-dev.1

  • Breaking changes Bumped minimum Flutter SDK requirement to 3.13. Consequently the minimum OS requirements for each platform has been updated as well
    • [Android] minimum Android version is now 4.4 (API level 19)
    • [iOS] minimum iOS version is now 11
    • [macOS] minimum macOS version is now 10.14
  • [Android] Breaking change removed the deprecated androidAllowWhileIdle parameter from zonedSchedule() and periodicallyShow() methods. androidScheduleMode is now a required parameter
  • Breaking change plugin has been fixed with regards to how it registers the platform-specific implementations of the plugin. Thanks to the PR from Kate. Any written tests done on the [FlutterLocalNotificationsPlugin] will need to manually call the registerWith() method that has been added to each implementation. This affects the following platforms/classes where the registerWith() method was added
    • [Android] AndroidFlutterLocalNotificationsPlugin
    • [iOS] IOSFlutterLocalNotificationsPlugin
    • [macOS] MacOSFlutterLocalNotificationsPlugin
  • Fixed example app to have the appropriate permissions for foreground services
  • Updated readme when it comes to setting up the AndroidManifest.xml file to include details of what's needed for foreground services. Note these details were already available in the API docs
Commits
  • 94a1170 [various] prepare for 18.0.0 release (#2442)
  • 15fe930 prepare for 18.0.0-dev.3 release (#2437)
  • 1da4bb7 added privacy manifest file to macOS implementation (#2436)
  • 8b8669e [flutter_local_notifications] removed all code related to UILocalNotification...
  • a3d3323 split out format workflow to occur on push (#2433)
  • 7265ae2 bumped dependency to linux 5.0.0 prerelease (#2422)
  • cc67070 updated various plugins for prerelease (#2421)
  • 28264a7 [flutter_local_notifications] updated minimum OS requirements to align with F...
  • d9789d8 fix: Fix platform initialization to allow mocking (#2418)
  • 34c1630 [flutter_local_notifications] fixed AndroidManifest issues in example for for...
  • Additional commits viewable in compare view


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
coderabbitai[bot] commented 3 weeks ago

[!IMPORTANT]

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

🪧 Tips ### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit , please review it.` - `Generate unit testing code for this file.` - `Open a follow-up GitHub issue for this discussion.` - Files and specific lines of code (under the "Files changed" tab): Tag `@coderabbitai` in a new review comment at the desired location with your query. Examples: - `@coderabbitai generate unit testing code for this file.` - `@coderabbitai modularize this function.` - PR comments: Tag `@coderabbitai` in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples: - `@coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.` - `@coderabbitai read src/utils.ts and generate unit testing code.` - `@coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.` - `@coderabbitai help me debug CodeRabbit configuration file.` Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. ### CodeRabbit Commands (Invoked using PR comments) - `@coderabbitai pause` to pause the reviews on a PR. - `@coderabbitai resume` to resume the paused reviews. - `@coderabbitai review` to trigger an incremental review. This is useful when automatic reviews are disabled for the repository. - `@coderabbitai full review` to do a full review from scratch and review all the files again. - `@coderabbitai summary` to regenerate the summary of the PR. - `@coderabbitai resolve` resolve all the CodeRabbit review comments. - `@coderabbitai configuration` to show the current CodeRabbit configuration for the repository. - `@coderabbitai help` to get help. ### Other keywords and placeholders - Add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed. - Add `@coderabbitai summary` to generate the high-level summary at a specific location in the PR description. - Add `@coderabbitai` anywhere in the PR title to generate the title automatically. ### Documentation and Community - Visit our [Documentation](https://coderabbit.ai/docs) for detailed information on how to use CodeRabbit. - Join our [Discord Community](http://discord.gg/coderabbit) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.
github-actions[bot] commented 3 weeks ago

Our Pull Request Approval Process

We have these basic policies to make the approval process smoother for our volunteer team.

Testing Your Code

Please make sure your code passes all tests. Our test code coverage system will fail if either of these two conditions occur:

  1. The overall code coverage drops below the target threshold of the repository
  2. Any file in the pull request has code coverage levels below the repository threshold

The process helps maintain the overall reliability of the code base and is a prerequisite for getting your PR approved. Assigned reviewers regularly review the PR queue and tend to focus on PRs that are passing.

Reviewers

Do not assign reviewers. Our Queue Monitors will review your PR and assign them. When your PR has been assigned reviewers contact them to get your code reviewed and approved via:

  1. comments in this PR or
  2. our slack channel

Reviewing Your Code

Your reviewer(s) will have the following roles:

  1. arbitrators of future discussions with other contributors about the validity of your changes
  2. point of contact for evaluating the validity of your work
  3. person who verifies matching issues by others that should be closed.
  4. person who gives general guidance in fixing your tests

Other

:dart: Please be considerate of our volunteers' time. Contacting the person who assigned the reviewers is not advised unless they ask for your input. Do not @ the person who did the assignment otherwise.