chore: change version number for release #18
Conversation
WalkthroughThe version string in the android/build.gradle.kts file was updated from "1.1.0" to "1.0.2". No other changes were made to the build script or its configuration. Changes
Note ⚡️ AI Code Reviews for VS Code, Cursor, WindsurfCodeRabbit now has a plugin for VS Code, Cursor and Windsurf. This brings AI code reviews directly in the code editor. Each commit is reviewed immediately, finding bugs before the PR is raised. Seamless context handoff to your AI code agent ensures that you can easily incorporate review feedback. Note ⚡️ Faster reviews with cachingCodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 16th. To opt out, configure ✨ Finishing Touches
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. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. 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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (1)
android/build.gradle.kts (1)
17-17:Details
❓ Verification inconclusive
Confirm version rollback intention & consider centralizing version management
Rolling back from"1.1.0"to"1.0.2"can conflict with existing artifacts on Maven Central—please verify that this downgrade is deliberate and aligns with your release strategy. Additionally, as a maintenance improvement, you might externalize theversionintogradle.properties(e.g.VERSION_NAME=1.0.2) and reference it here to keep versioning consistent across modules.
🏁 Script executed:
#!/bin/bash # Verify existing published versions of com.formbricks:android on Maven Central curl -s "https://search.maven.org/solrsearch/select?q=g:%22com.formbricks%22+AND+a:%22android%22&rows=20&wt=json" \ | jq -r '.response.docs[].v'Length of output: 144
Confirm version rollback intention & centralize version management
I wasn’t able to find any published versions forcom.formbricks:androidon Maven Central—please verify manually that downgrading from"1.1.0"to"1.0.2"is deliberate and fits your release strategy. As a long-term improvement, consider moving theversionintogradle.properties(e.g.VERSION_NAME=1.0.2) and referencing it here so all modules stay in sync.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
android/build.gradle.kts(1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (2)
- GitHub Check: Analyze (java-kotlin)
- GitHub Check: SonarCloud
|
This pull request includes a small change to the
android/build.gradle.ktsfile. The change updates theversionproperty from1.1.0to1.0.2to reflect a version rollback.Summary by CodeRabbit