Release v2.1.5

[yuni-ju]

No description provided.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 93a01017-58fa-4e9c-9a6f-a349ffc8dcaf

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch release/2.1.5

---

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

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 6afcf9a89d

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

Preserve existing QA bot branches on reruns

When this workflow is rerun for an issue that already has a feature/issue-N PR, this line deletes the remote branch before recreating it; git push -h documents --delete as “delete refs”. In the inspected .github/workflows/qa-bot.yml flow, a labeled-event rerun or manual rerun would therefore discard any reviewer/manual commits pushed to that bot branch and can leave the existing PR without its head branch (or make the subsequent gh pr create conflict with the existing PR). Prefer updating/resetting the branch intentionally only after checking for an open PR, or push with --force-with-lease to a bot-owned branch when that destructive behavior is explicitly desired.

Useful? React with 👍 / 👎.

[yuni-ju]

Play Store에 올라와있는 앱의 versionCode 이슈로 브랜치 새로 생성하겠습니다