[REFACTOR/#253] Release 환경 Proguard 설정을 수정합니다.

[MoonsuKang]

📌 ISSUE

closed #253

📄 Work Description

• 릴리즈 빌드 시 Proguard 설정을 disable로 설정.

✨ PR Point

release 환경에서 기본적으로 proguard설정이 들어가 앱 빌드 시 문제가 생기는 걸 확인 안했습니다ㅠㅠㅠ

📸 ScreenShot/Video

Summary by CodeRabbit

• Chores
  • Increased the application’s version number for the current release.
  • Adjusted release build optimizations to modify resource processing during production builds.

[coderabbitai]

Walkthrough

This pull request updates the Android app’s build configuration. In the app/build.gradle.kts file, the version code is incremented from 23 to 24. Additionally, in the release build type, both isMinifyEnabled and isShrinkResources are switched from true to false. These changes affect the application versioning and adjust build optimizations for the release environment.

Changes

File	Change Summary
app/build.gradle.kts	Updated versionCode from 23 to 24; modified release build type by setting isMinifyEnabled and isShrinkResources to false

Assessment against linked issues

Objective	Addressed	Explanation
Modify Release environment Proguard settings (#253)	❓	Disables minification and resource shrinking rather than adding new Proguard rules.

Possibly related PRs

• [REFACTOR/#249] signing 설정 수정 및 버전 수정 #250: Involves similar changes to versioning and release build properties within the same app/build.gradle.kts file.

Suggested labels

♻️ REFACTOR

Suggested reviewers

• SYAAINN

Poem

I'm the bunny, hopping in code delight,
Version bumped high, shining ever so bright.
Minification takes a little snooze today,
Resources now free to frolic and play.
With twitching whiskers, I cheer this fix anew—
Hoppy coding days are here, just for you!

Warning

Review ran into problems

🔥 Problems

Git: Failed to clone repository. Please run the @coderabbitai full review command to re-trigger a full review. If the issue persists, set path_filters to include or exclude specific files.

✨ Finishing Touches

• 📝 Generate Docstrings

---

🪧 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.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

app/build.gradle.kts (1)

62-65: Review Proguard File References

Although Proguard optimizations are disabled in the release build, the proguardFiles(...) configuration still exists in this block. If minification and resource shrinking are no longer needed, consider removing these references to reduce potential confusion and simplify the build configuration. If they are kept for historical reasons or potential future use, please document the rationale.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 4f5da1f and 9121d8e.

📒 Files selected for processing (1)

• app/build.gradle.kts (2 hunks)

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

• GitHub Check: build

🔇 Additional comments (2)

app/build.gradle.kts (2)

28-28: Version Code Bump to 24

The version code in the defaultConfig section has been updated from 23 to 24 as part of this release. Please ensure that the associated versioning strategy (including versionName changes, if needed) is consistently documented and communicated.

---

59-60: Disabling Code Minification and Resource Shrinking in Release

The release build configuration now explicitly disables both code minification (isMinifyEnabled = false) and resource shrinking (isShrinkResources = false). This change directly addresses the issues encountered with Proguard in the release environment. Please verify that this configuration meets the desired trade-offs (e.g., APK size, performance, and security) and that it has been approved by your team.