Increment versions for new release

[BenjaminSsempala]

Summary of Changes (What does this PR do?)

• Increment versions for new release

Summary by CodeRabbit

• New Features

  • Introduced a "Pidgin Translations" section in the release notes, enhancing documentation for users.

• Bug Fixes

  • Continued focus on improving user experience with various bug fixes.

• Performance Enhancements

  • Included updates aimed at enhancing the overall performance of the application.

• Version Update

  • Incremented application version to 2.1.3, indicating new features and improvements.

[coderabbitai]

Walkthrough

Walkthrough

The changes involve updates to the release_notes.txt and pubspec.yaml files for a mobile application. A new section for "Pidgin Translations" has been added to the release notes, enhancing documentation on recent updates. Additionally, the version number in the pubspec.yaml file has been incremented, indicating a new release of the application, while the SDK environment specifications remain unchanged.

Changes

File	Change Summary
mobile/android/fastlane/release_notes.txt	Added "Pidgin Translations" section to document new translations.
mobile/pubspec.yaml	Updated version from 2.1.2+20057 to 2.1.3+20058.

Poem

In notes of release, a new tale we weave,
Pidgin now speaks, in words we believe.
Version ascends, a step up the way,
Enhancements and fixes, brightening the day!
Celebrate change, let the updates flow,
In the world of apps, we're ready to grow! 🎉

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  -- I pushed a fix in commit <commit_id>, 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 generate interesting stats about this repository and render them as a table.
  -- @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.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

Tip

Early access features: enabled

We are currently testing the following features in early access:

• OpenAI o1 for code reviews: OpenAI's new o1 model is being tested for code reviews. This model has advanced reasoning capabilities and can provide more nuanced feedback on your code.

Note:

• You can enable or disable early access features from the CodeRabbit UI or by updating the CodeRabbit configuration file.
• • Please join our Discord Community to provide feedback and report issues on the discussion post.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 7.77%. Comparing base (b91ca87) to head (7fad1b9).

Additional details and impacted files

@@             Coverage Diff             @@
##           staging   #2172       +/-   ##
===========================================
- Coverage   100.00%   7.77%   -92.23%     
===========================================
  Files            1     166      +165     
  Lines            5   11973    +11968     
  Branches         2       0        -2     
===========================================
+ Hits             5     931      +926     
- Misses           0   11042    +11042     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[coderabbitai]

Actionable comments posted: 0

Outside diff range and nitpick comments (1)

mobile/android/fastlane/release_notes.txt (1)

1-3: Standardize Capitalization in Release Notes

I noticed that "Performance enhancements" uses lowercase for "enhancements," while the other entries are fully capitalized. For consistency and a polished appearance, consider capitalizing "Enhancements" to match the other headings.

Here's the suggested change:

 Pidgin Translations
 Bug Fixes
-Performance enhancements
+Performance Enhancements

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between b91ca87 and 7fad1b9.

Files selected for processing (2)

• mobile/android/fastlane/release_notes.txt (1 hunks)
• mobile/pubspec.yaml (1 hunks)

Files skipped from review due to trivial changes (1)

• mobile/pubspec.yaml

[Baalmart]

thanks @BenjaminSsempala