Skip to content

fix: Ci build issue regarding release signin config#333

Merged
aritra-tech merged 3 commits into
masterfrom
ci_build_fix
Jun 15, 2025
Merged

fix: Ci build issue regarding release signin config#333
aritra-tech merged 3 commits into
masterfrom
ci_build_fix

Conversation

@aritra-tech
Copy link
Copy Markdown
Member

@aritra-tech aritra-tech commented Jun 15, 2025

Summary by CodeRabbit

  • New Features
    • Updated application ID, version code, and version name.
    • Added baseline profile entries for improved performance on different Android versions.
  • Improvements
    • Enhanced build process by separating debug and release builds and clarifying keystore path handling.
    • Improved signing configuration to support fallback to system properties.
    • Updated Kotlin compiler extension and Compose dependencies.
    • Switched Room compiler dependency to KSP for better performance.
    • Disabled database schema export during compilation.
  • Chores
    • Upgraded Kotlin Android plugin version.
    • Minor formatting improvements.

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Jun 15, 2025

Walkthrough

The changes update build configurations and metadata for an Android project. Debug and release builds are now separated in the CI workflow, with improved handling of signing credentials. The Room database disables schema export, dependency versions are updated, and metadata reflects a new application ID, version, and baseline profiles.

Changes

File(s) Change Summary
.github/workflows/ci_build.yml Split debug and release build steps, clarified signing parameters, and made keystore path absolute in the CI workflow.
app/build.gradle.kts, build.gradle.kts Improved signing config to use system properties as fallback, updated Compose and Kotlin plugin versions, switched Room to KSP, cleanup.
app/release/output-metadata.json Changed application ID, version code/name, added baseline profiles, and new minSdkVersionForDexing field.
app/src/main/java/com/aritradas/uncrack/data/db/CardDatabase.kt Added exportSchema = false to the Room database annotation.

Sequence Diagram(s)

sequenceDiagram
    participant CI as GitHub Actions CI
    participant Gradle as Gradle Build System

    CI->>Gradle: ./gradlew assembleDebug
    Gradle-->>CI: Build debug APK (no signing)
    CI->>Gradle: ./gradlew assembleRelease (with signing params)
    Gradle-->>CI: Build release APK (signed)
Loading

Poem

In the warren where code does compile,
Debug and release now march in style.
With keystores set and versions anew,
The bunny hops—Compose shines through!
Baseline profiles tucked in tight,
Database schema out of sight—
A carrot for builds that run just right! 🥕

✨ Finishing Touches
  • 📝 Generate Docstrings

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
🪧 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.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 explain its main purpose.
    • @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.

Support

Need 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)

  • @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 generate sequence diagram to generate a sequence diagram of the changes in this 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.

Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (2)
.github/workflows/ci_build.yml (1)

121-121: Remove trailing whitespace
Line 121 contains unnecessary spaces. Clean up to satisfy YAML lint.

🧰 Tools
🪛 YAMLlint (1.37.1)

[error] 121-121: trailing spaces

(trailing-spaces)

app/build.gradle.kts (1)

44-57: Enhance signing config fallback logic
The chained fallback from local.properties to system props to defaults is robust, but consider failing the build when critical values (e.g., storePassword) are empty to avoid silent misconfigurations. You may also reference rootProject.file(...) for clarity.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 5deccb8 and 437df7c.

📒 Files selected for processing (5)
  • .github/workflows/ci_build.yml (1 hunks)
  • app/build.gradle.kts (4 hunks)
  • app/release/output-metadata.json (1 hunks)
  • app/src/main/java/com/aritradas/uncrack/data/db/CardDatabase.kt (2 hunks)
  • build.gradle.kts (1 hunks)
🧰 Additional context used
🪛 YAMLlint (1.37.1)
.github/workflows/ci_build.yml

[error] 121-121: trailing spaces

(trailing-spaces)

⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Build
🔇 Additional comments (12)
build.gradle.kts (2)

12-12: Plugin version bump to Kotlin Android 1.9.22
This is a minor version upgrade and aligns with other build components.


20-20: No functional changes in this closing brace; configuration remains intact.

app/src/main/java/com/aritradas/uncrack/data/db/CardDatabase.kt (2)

12-13: Disable Room schema export
Setting exportSchema = false prevents generating the database schema into JSON files. If you intend to maintain versioned schemas for migrations or audits, consider enabling schema export and committing them.


40-40: Closing brace only; no substantive change.

app/release/output-metadata.json (5)

7-7: Update applicationId
Changed to com.aritradas.uncrack to reflect the new package ownership. Ensure AndroidManifest.xml and other references align.


14-15: Bump versionCode and versionName
Updated to 16 and "3.2.4". Confirm that version.properties or other version sources remain consistent with these values.


19-19: elementType property adjustment; no functional impact on the APK metadata.


20-34: Add baseline profile configurations
New baselineProfiles entries for API 28–30 and 31+ are included. Verify that the referenced files exist under app/src/main/baselineProfiles and that they’re packaged appropriately.


36-36: Define minSdkVersionForDexing
Set to 24, matching the module’s minSdk. This aligns dexing with runtime support.

.github/workflows/ci_build.yml (1)

119-127: Separate debug and release builds with explicit signing
Running assembleDebug without signing and assembleRelease with injected keystore parameters matches the updated signing config. Good alignment with app/build.gradle.kts.

🧰 Tools
🪛 YAMLlint (1.37.1)

[error] 121-121: trailing spaces

(trailing-spaces)

app/build.gradle.kts (2)

89-89: Upgrade Compose compiler extension
Updated to "1.5.8" to align with the latest BOM and plugin versions.


102-102: Apply Compose BOM to Android tests
Adding androidTestImplementation(composeBom) ensures consistent Compose dependencies in instrumentation tests.

@aritra-tech aritra-tech merged commit 106447e into master Jun 15, 2025
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant