Release 3.1.27

[jo-elimu]

https://github.com/elimu-ai/analytics/releases/tag/3.1.27

Resolves #177

Updated dependencies:

• chore(deps): analytics 3.1.27 vitabu#120
• chore(deps): analytics 3.1.27 kukariri#36
• chore(deps): analytics 3.1.27 herufi#40
• chore(deps): analytics 3.1.27 content-provider#146
• chore(deps): analytics 3.1.27 image-picker#20
• chore(deps): analytics 3.1.27 sound-cards#16

Summary by CodeRabbit

• Chores
  • Updated the application and utility library to version 3.1.27, ensuring users receive the latest release improvements.
  • Optimized the build workflow so that all components are properly assembled before packaging, which enhances overall release stability and reliability.
  • These continuous improvements contribute to delivering a noticeably smoother update experience and improved system performance.

[coderabbitai]

Walkthrough

The pull request updates versioning details for the Android application and its associated library. In the application module, the version code and version name are incremented, reflecting a new release. In the library module, similar version updates are applied to both the default configuration and publication settings. Additionally, a task dependency is established in the library build script so that bundling the release AAR is executed prior to publishing it to the local Maven repository.

Changes

File(s)	Change Summary
app/build.gradle	Updated versionCode from 3001022 to 3001027 and versionName from "3.1.22-SNAPSHOT" to "3.1.27".
utils/build.gradle	Updated versionName in defaultConfig and MavenPublication from "3.1.22-SNAPSHOT" to "3.1.27"; added task dependency ensuring publishReleasePublicationToMavenLocal runs after :utils:bundleReleaseAar.

Sequence Diagram(s)

sequenceDiagram
    participant Bundle as :utils:bundleReleaseAar
    participant Publish as publishReleasePublicationToMavenLocal

    Bundle->>Publish: Completes execution
    Publish-->>Bundle: Dependency enforced (runs after bundling)

Loading

Possibly related PRs

• refactor: 'utils' --> 'release' #178: Involves similar versioning updates in utils/build.gradle, mirroring the switch from snapshot to release version.
• Upgrade Android Gradle build tools to 8.1.4 #174: Contains versioning updates in app/build.gradle, directly related to the changes made here.
• Release 3.1.20 #158: Focuses on updating the version name in the library module, ensuring consistency across the project.

Suggested reviewers

• nya-elimu

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c9ac416 and 7c9b565.

📒 Files selected for processing (2)

• app/build.gradle (1 hunks)
• utils/build.gradle (3 hunks)

✅ Files skipped from review due to trivial changes (1)

• app/build.gradle

⏰ Context from checks skipped due to timeout of 90000ms (2)

• GitHub Check: build (windows-latest, 17)
• GitHub Check: build (macos-latest, 17)

🔇 Additional comments (4)

utils/build.gradle (4)

13-13: Version Name Updated in defaultConfig
The versionName "3.1.27" update replaces the old snapshot version and aligns with the new release. However, note that the PR title mentions "Release 3.1.26". Please verify that the intended version is indeed 3.1.27.

---

40-40: Maven Publication Version Update
The publication version is updated to '3.1.27', which matches the new versionName. Ensure that this update is consistent with your release strategy, especially given the discrepancy with the PR title.

---

52-54: Task Dependency for Publishing Order
The new task dependency using tasks.named("publishReleasePublicationToMavenLocal") { mustRunAfter(":utils:bundleReleaseAar") } ensures that the AAR bundling completes before publishing to the local Maven repository. This ordering is important to avoid publishing incomplete artifacts. Confirm that the referenced task :utils:bundleReleaseAar exists and works as expected.

---

1-55: Overall Versioning Consistency Check
There is a version mismatch between the PR title ("Release 3.1.26") and the versions updated in this file ("3.1.27"). Please review and update the version numbers across the project to maintain consistency.

---

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 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 generate docstrings to generate docstrings for this PR. (Beta)
• @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.