Prepare release 1.0.4

[tuancoltech]

Prepare release 1.0.4

Summary by CodeRabbit

• Chores
  • Updated the library's version details to ensure consistency ahead of the new release.

[coderabbitai]

Walkthrough

The pull request updates the versioning information in the utils/build.gradle file. The libVersion is incremented from '1.0.3-SNAPSHOT' to '1.0.4-SNAPSHOT', and the versionCode is increased from 1000003 to 1000004. These changes are part of the release preparation process to reflect a new version.

Changes

File	Change Summary
utils/build.gradle	Updated libVersion from '1.0.3-SNAPSHOT' to '1.0.4-SNAPSHOT' and versionCode from 1000003 to 1000004

Possibly related PRs

• Add versionName/versionCode for utils's build.gradle #2: Updates the versioning details in utils/build.gradle, building upon earlier modifications.
• Release 1.0.2 #5: Introduces similar updates to libVersion and versionCode, indicating a direct relationship in versioning changes.

Suggested reviewers

• jo-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 1b59b0e and e240529.

📒 Files selected for processing (1)

• utils/build.gradle (2 hunks)

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

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

🔇 Additional comments (2)

utils/build.gradle (2)

10-10: Version String Update Verification

The libVersion variable is updated from '1.0.3-SNAPSHOT' to '1.0.4-SNAPSHOT' as expected for this release preparation. Please verify that the inclusion of the -SNAPSHOT suffix aligns with your release strategy and that all related documentation or CI pipelines are updated accordingly.

---

21-21: Version Code Increment Check

The versionCode is correctly bumped from 1000003 to 1000004, ensuring that the internal versioning is in sync with the new release. Double-check that this change is consistently applied across any modules or build configurations that reference the version code.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @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.