Skip to main content

RuneLite Update Automation

.github/workflows/runelite-update.yml checks RuneLite's official Maven metadata every Tuesday at 16:00 and 20:00 UTC. You can also run it manually from GitHub Actions.

When the workflow finds a newer release, it opens or refreshes one draft pull request that changes the runeLiteVersion pin in build.gradle and runs the full Gradle build. It never merges or publishes the update.

Why the pull request remains a draft​

A RuneLite release can carry a game revision change. n3Plugins has revision-sensitive packet mappings, widget resources, ID maps, and reference artifacts; a dependency-only upgrade cannot establish that those are still correct.

Before merging the generated pull request, you must:

  1. Acquire version-matched RuneLite and injected-client artifacts.
  2. Run the applicable revision analysis and mapping tests.
  3. Refresh revision-owned widget and ID-map resources when required.
  4. Update N3PLUGINS_SOURCE_OF_TRUTH.md with the verified version and revision.
  5. Run the required build and live-client checks.

The draft pull request records the workflow's Gradle result. A passing build provides useful compatibility evidence, but it does not replace live game verification.