Repository navigation
build: add standard Plugin Hub packaging and CI feedback - #103
Merged
Merged
Conversation
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. Note Currently processing new changes in this PR. This may take a few minutes, please wait... ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (8)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
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. Comment |
AntonyGarand
force-pushed
the
build/standard-plugin-hub-ci
branch
from
September 30, 2026 02:03
d04e4e2 to
5de0019
Compare
AntonyGarand
marked this pull request as ready for review
September 30, 2026 02:14
This was referenced Oct 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Plugin Hub maintainers require
build=standardfor the review bot (discussion). Running the same packaging checks in this repository exposes build and API problems before a Hub submission.This PR is rebased onto
masterata410537468a84459f654304d9c9028d3e5ccb820, the latest accepted Plugin Hub revision. The restored published version uses JSON storage, so the previous SQLite compilation blocker is no longer present. The intended impact is earlier developer feedback; gameplay behavior is unchanged.Summary
runelite-plugin.properties, retaining local Gradle development and test tasks.Validation
5de0019: Java 11 build/tests and official RuneLite Plugin Hub packaging both succeeded, with reports and package artifacts uploaded../gradlew clean build: 58 tests passed, zero failures or skips, including six CSV export tests.To reproduce the Hub check on Linux with Java 11 after checking out this pushed branch:
PLUGIN_REPOSITORY=Flipping-Utilities/rl-plugin \ PLUGIN_COMMIT="$(git rev-parse HEAD)" \ bash .github/scripts/check-plugin-hub.shNotes
The checks reproduce RuneLite's packaging feedback, not its separate review bot or maintainer approval. This PR does not update the Hub manifest or publish a plugin release.
Agent session:
codex resume 01a0f008-f252-7760-9f1c-ae5973d6b587· Model:gpt-6-astra· Reasoning:ultra🤖
cb-ship:created v1 skill@1.0.13