Repository navigation
Configure Oracle JDK 25/27, upgrade Paper 26.3, and fix CI - #1
Merged
Merged
Conversation
Replace the stale Maven workflow with a pinned Java 25 and Gradle build. Resolve BlueMapAPI and PlaceholderAPI from their official repositories so clean checkouts can compile and package the plugin without local server jars.
Select the exact release JDK through JAVA_HOME for Gradle, compilation, tests, and CI while retaining Java 25 bytecode and Paper 26.2 build 84. Add isolated dual-runtime smoke checks and preserve historical verification records. Handle current and staged PaperScript checksums independently.
Resolve and validate installed Oracle JDKs dynamically, enforce compiler and test toolchains, and reject automatic provisioning or conflicting overrides. Update local build commands, CI configuration, smoke runtime selection, and documentation. Verified the standalone selection with clean check: 3 Java tests, 15 Python tests, and Java 25 bytecode checks. Keep the pre-existing Paper upgrade and fixture work outside this commit.
Pin the latest verified Paper 26.3 STABLE server and exact API, lock dependencies, and prepare isolated fixtures without changing historical servers. Keep normal builds free of deployment. Align smoke fixture selection with release configuration, guard direct Java launches before deployment, and make smoke shutdown cleanup reliable when stdin closes. Record official API/default review and local verification. Validation: clean locked build, 3 Java tests, 48 Python tests, 93 checks across four Paper lifecycles on Oracle 27, and live/stopped deployment-guard checks. No deployment or remote CI run.
GitHub recorded pushes but suppressed inherited workflows behind the fork activation gate, despite enabled Actions permissions, an active workflow, and a successful manual run. Enable the fork's workflows in the Actions UI and document how to verify an event=push run for the exact commit. Keep the existing unrestricted push trigger, build-only job, and read-only workflow permissions. This documentation push exercises the repaired automatic trigger without deploying or starting Paper servers.
Replace the Node 20 action with the current Node 24 release to remove GitHub Actions' runtime deprecation warning. Pin the official release commit and retain the artifact name, path, failure policy, and retention.
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.
Update the maintained fork's build and verification workflow for Paper 26.3 build 222 STABLE, keeping plugin version 2.0.2 and release build 031.
Changes
--release 25; run Java tests and child JVMs on Oracle JDK 27. Resolve installed macOS JDKs dynamically, validate their actual versions and vendor, and reject downloads or conflicting toolchain settings.upload-artifactv7.0.2 to remove the Node.js 20 deprecation warning.Validation
This PR targets
maininmrfdev/1MB-MapHide. No merge or deployment is part of this change; the CI job does not start servers.