fix(creeper-fear): support Purpur 26.3 #1

Merged
dmg merged 1 commits from ticket-405-support-purpur-26-3 into main 2026-10-17 00:37:37 +00:00
Owner

OpenProject: https://project.dmg.games/work_packages/405

Scope

  • compile and test with Java 25 against Purpur API 26.3 build 2651
  • pin native verification to the approved build-2651 URL and SHA-256
  • set and verify packaged api-version: 26.3
  • load, enable, schema-check, and disable the packaged entrypoint on native Purpur classes
  • preserve SQLite packaging/schema, progression, damage attribution, identities, cancellation, and state
  • document the exact supported platform and verification boundary

No production Java file changes were required.

Verification

  • meaningful RED: 2/3 distribution tests failed against old 26.2 metadata/build pins
  • focused distribution GREEN: 3/3
  • native lifecycle: 1/1
  • ./gradlew clean check jar: 40 tests total (39 ordinary + 1 native), zero failures/errors/skips; all ten tasks executed
  • candidate JAR: 29 Java 25 plugin classes, SQLite driver/service/multi-release packaging retained, no API/server/ProtocolLib/test payload
  • tested commit: ed1e9a49328bc49593e49a3b63bb96f996c19172
  • tested tree: cd878aa7e62b24c63da8777b702eb036b6e81723
  • target base: 49627d58b56deeff5552b451f7baa4f778e064a4
  • 52 tracked-input aggregate SHA-256: 4de049c82e43e29b6c914f42be6ae7958393e43943901dd5cdecfde82f68ca69

Publication effect

Merging to main triggers semantic release. Ticket completion remains blocked until current-head checks pass, the Gitea merge tree equals the tested tree, and the exact merged commit has a verified versioned tag and downloadable JAR. No GitOps, deployment, live-server, secret, repository-setting, or CI/release-tooling change is included.

OpenProject: https://project.dmg.games/work_packages/405 ## Scope - compile and test with Java 25 against Purpur API 26.3 build 2651 - pin native verification to the approved build-2651 URL and SHA-256 - set and verify packaged `api-version: 26.3` - load, enable, schema-check, and disable the packaged entrypoint on native Purpur classes - preserve SQLite packaging/schema, progression, damage attribution, identities, cancellation, and state - document the exact supported platform and verification boundary No production Java file changes were required. ## Verification - meaningful RED: 2/3 distribution tests failed against old 26.2 metadata/build pins - focused distribution GREEN: 3/3 - native lifecycle: 1/1 - `./gradlew clean check jar`: 40 tests total (39 ordinary + 1 native), zero failures/errors/skips; all ten tasks executed - candidate JAR: 29 Java 25 plugin classes, SQLite driver/service/multi-release packaging retained, no API/server/ProtocolLib/test payload - tested commit: `ed1e9a49328bc49593e49a3b63bb96f996c19172` - tested tree: `cd878aa7e62b24c63da8777b702eb036b6e81723` - target base: `49627d58b56deeff5552b451f7baa4f778e064a4` - 52 tracked-input aggregate SHA-256: `4de049c82e43e29b6c914f42be6ae7958393e43943901dd5cdecfde82f68ca69` ## Publication effect Merging to `main` triggers semantic release. Ticket completion remains blocked until current-head checks pass, the Gitea merge tree equals the tested tree, and the exact merged commit has a verified versioned tag and downloadable JAR. No GitOps, deployment, live-server, secret, repository-setting, or CI/release-tooling change is included.
dmg added 1 commit 2026-10-17 00:34:30 +00:00
fix(creeper-fear): support Purpur 26.3
CI / build (push) Successful in 1m6s
CI / build (pull_request) Successful in 1m10s
ed1e9a4932
dmg merged commit 0da7644954 into main 2026-10-17 00:37:37 +00:00
Sign in to join this conversation.
No Reviewers
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: dmg/purpur-creeper-fear#1