빌드 최신화

[unam98]

📌 개요

✨ 작업 내용

• 장시간 빌드하지 않아 최신화가 필요한 부분을 갱신해주었습니다.

✨ PR 포인트

📸 스크린샷/동영상

Summary by CodeRabbit

• Chores

  • Upgraded Java/Kotlin runtime to 17 for improved performance and compatibility.
  • Updated Naver Map SDK to a newer version, enhancing map stability and potential features.
  • Refreshed repository configuration for dependency resolution.

• Refactor

  • Streamlined internal service wiring; no user-facing changes.

Note: These updates aim to improve app stability, performance, and compatibility. No changes to user workflows or UI.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

Build configuration updates include Java/Kotlin version bumps, a Naver Map SDK upgrade, and a repository URL change. Dependency injection changes remove a debug-only BannerService provider and add a FirebaseFirestore provider in the main ServiceModule. Keystore path adjusted in signing config.

Changes

Cohort / File(s)	Summary
Build and dependency configuration app/build.gradle, settings.gradle	Updated Java to 17, Kotlin jvmTarget to 17, Naver Map SDK 3.16.1→3.22.1, adjusted keystore path, and switched Naver Maven repository URL.
DI modules app/src/debug/java/.../DebugServiceModule.kt, app/src/main/java/.../ServiceModule.kt	Removed Firestore-based BannerService provider from debug module; added provideFirebaseFirestore() (@singleton, @provides) to main ServiceModule; refined imports.

Sequence Diagram(s)

sequenceDiagram
  autonumber
  actor App as Application
  participant DI as ServiceModule (Hilt)
  participant FB as Firebase SDK

  App->>DI: Request FirebaseFirestore
  activate DI
  DI->>FB: Firebase.firestore
  FB-->>DI: FirebaseFirestore instance
  DI-->>App: Provide FirebaseFirestore
  deactivate DI

  Note over App,DI: Debug build no longer provides BannerService via Firestore

Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

I thump my paws on versioned ground,
Seventeen carrots neatly found;
Maps refreshed, the routes align,
A keystore hop—now all is fine.
Firestore springs from DI’s burrow,
Debug banners fade like dusk to morrow.
Onward, ship—ears up, let’s go! 🥕✨

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between a6e37c3 and 82b17b2.

📒 Files selected for processing (4)

• app/build.gradle (3 hunks)
• app/src/debug/java/com/runnect/runnect/developer/di/DebugServiceModule.kt (0 hunks)
• app/src/main/java/com/runnect/runnect/di/ServiceModule.kt (2 hunks)
• settings.gradle (1 hunks)

✨ Finishing Touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch feature/fix-build-error

---

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.
  • 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.
• 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

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

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• 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.