2.0.43

[chsami]

No description provided.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

This PR bumps the Maven parent POM version from 1.12.5.1 to 1.12.5.2 across multiple module files (cache, runelite-api, runelite-client, runelite-jshell, runelite-maven-plugin). Additionally, runelite-client/pom.xml updates the microbot.version property from 2.0.43 to 2.0.44. The MiningPlugin adds handling for two new rock object IDs (LEADROCK1_EMPTY and NICKELROCK1_EMPTY). MiningSiteLocation expands with new mining site enum constants and introduces LEAD and NICKEL ore types.

Possibly related PRs

• 2.0.36.2 patch runelite version #1592: Updates Maven parent <version> entries across the same set of module pom files
• chore(pom): update parent version to 1.12.5.1 and microbot version to… #1610: Modifies both parent POM version and microbot.version property in the same files
• 2.0.17 #1549: Updates the microbot.version property in runelite-client/pom.xml

✨ Finishing touches

• 📝 Generate docstrings

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 9565f08 and a037941.

⛔ Files ignored due to path filters (1)

• runelite-client/src/main/resources/net/runelite/client/plugins/microbot/shortestpath/collision-map.zip is excluded by !**/*.zip

📒 Files selected for processing (8)

• cache/pom.xml (1 hunks)
• pom.xml (1 hunks)
• runelite-api/pom.xml (1 hunks)
• runelite-client/pom.xml (2 hunks)
• runelite-client/src/main/java/net/runelite/client/plugins/mining/MiningPlugin.java (1 hunks)
• runelite-client/src/main/java/net/runelite/client/plugins/worldmap/MiningSiteLocation.java (7 hunks)
• runelite-jshell/pom.xml (1 hunks)
• runelite-maven-plugin/pom.xml (1 hunks)

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

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