fix(deps): update dependency androidx.test.ext:junit to v1.3.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
androidx.test.ext:junit	1.2.1 → 1.3.0

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[codetortoiseai]

@coderabbitai review

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository.

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.

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

Walkthrough

The version alias junitVersion in the gradle/libs.versions.toml file was updated from "1.2.1" to "1.3.0". This change updates the version of the androidx-junit library used in the project. No other libraries, versions, or plugins were modified.

Changes

Cohort / File(s)	Change Summary
JUnit Version Update gradle/libs.versions.toml	Updated junitVersion from "1.2.1" to "1.3.0" in the [versions] section.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

A hop and a skip, the versions align,
JUnit hops forward—now 1.3.0 in line.
Bugs beware, tests shine anew,
With every update, our confidence grew.
🐇✨

---

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

Support

Need help? Join our Discord community for assistance with any issues or questions.

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

[coderabbitai]

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

gradle/libs.versions.toml (1)

5-6: Alias naming clarity

Having both junit (plain JUnit 4) and junitVersion (AndroidX extension) can be misleading. A name like androidxTestJunit would better convey its purpose and avoid accidental mix-ups.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 4145d1e and 8570321.

📒 Files selected for processing (1)

• gradle/libs.versions.toml (1 hunks)

🧰 Additional context used

🧠 Learnings (1)

gradle/libs.versions.toml (10)

Learnt from: CR
PR: testpress/TPStreamsAndroidPlayer#0
File: .cursor/rules/testing-guidelines.mdc:0-0
Timestamp: 2025-07-03T12:34:03.018Z
Learning: Applies to app/src/test/java/com/package/**/*.kt : Implement UI tests using Compose testing framework.

Learnt from: CR
PR: testpress/TPStreamsAndroidPlayer#0
File: .cursor/rules/testing-guidelines.mdc:0-0
Timestamp: 2025-07-03T12:34:03.018Z
Learning: Applies to app/src/test/java/com/package/**/*.kt : Write unit tests for ViewModels and UseCases.

Learnt from: CR
PR: testpress/TPStreamsAndroidPlayer#0
File: .cursor/rules/general-best-practices.mdc:0-0
Timestamp: 2025-07-18T14:40:39.393Z
Learning: Applies to app/src/main/java/com/package/**/*.kt : Follow Material Design 3 guidelines and components.

Learnt from: CR
PR: testpress/TPStreamsAndroidPlayer#0
File: .cursor/rules/testing-guidelines.mdc:0-0
Timestamp: 2025-07-03T12:34:03.018Z
Learning: Applies to app/src/test/java/com/package/**/*.kt : Use proper testing coroutine dispatchers.

Learnt from: CR
PR: testpress/TPStreamsAndroidPlayer#0
File: .cursor/rules/testing-guidelines.mdc:0-0
Timestamp: 2025-07-03T12:34:03.018Z
Learning: Applies to app/src/test/java/com/package/**/*.kt : Use fake repositories for testing.

Learnt from: CR
PR: testpress/TPStreamsAndroidPlayer#0
File: .cursor/rules/general-best-practices.mdc:0-0
Timestamp: 2025-07-18T14:40:39.393Z
Learning: Applies to app/src/main/java/com/package/**/*.kt : Implement dependency injection using Hilt.

Learnt from: CR
PR: testpress/TPStreamsAndroidPlayer#0
File: .cursor/rules/ui-guidelines.mdc:0-0
Timestamp: 2025-07-22T13:57:41.044Z
Learning: Applies to app/src/main/java/com/package/presentation/**/*.kt : Use proper Compose modifiers ordering

Learnt from: CR
PR: testpress/TPStreamsAndroidPlayer#0
File: .cursor/rules/testing-guidelines.mdc:0-0
Timestamp: 2025-07-03T12:34:03.018Z
Learning: Applies to app/src/test/java/com/package/**/*.kt : Implement proper test coverage.

Learnt from: CR
PR: testpress/TPStreamsAndroidPlayer#0
File: .cursor/rules/performance-guidelines.mdc:0-0
Timestamp: 2025-07-18T14:40:52.313Z
Learning: Applies to app/src/main/java/com/package/**/*.kt : Follow proper lifecycle awareness in Jetpack Compose

Learnt from: CR
PR: testpress/TPStreamsAndroidPlayer#0
File: .cursor/rules/general-best-practices.mdc:0-0
Timestamp: 2025-07-18T14:40:39.393Z
Learning: Applies to app/src/main/java/com/package/**/*.kt : Use Compose navigation for screen management.

🔇 Additional comments (1)

gradle/libs.versions.toml (1)

6-6: Confirm compatibility of androidx.test.ext:junit 1.3.0 with your instrumentation stack

The upgrade is benign on paper, but 1.3.0 aligns with AndroidX-Test 1.5+ and may surface API-level or transitive conflicts (e.g., androidx.test:core or runner mismatches). Please run your full connected/instrumentation test suite and check for:

• Duplicate class warnings in the APK
• Runtime NoClassDefFoundError or JUnitRuntimeException
• Gradle dependency resolution downgrades/forced versions

If all tests pass, nothing else to do.