fix(base): support Purpur 26.3 #1

Merged
dmg merged 1 commits from ticket-403-support-purpur-26-3 into main 2026-10-16 23:53:41 +00:00
Owner

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

Scope

  • build and test with Java 25 against Purpur API 26.3 build 2651
  • pin native verification to the approved build 2651 URL and SHA-256
  • adapt native packet and registry test boundaries to the 26.3 API
  • preserve runtime identity, metadata compatibility floor, behavior, and packaged exclusions
  • document the exact supported platform

Verification

  • meaningful RED: 26.3 platform assertion failed against the old 26.2 build
  • meaningful native RED: 26.3 exposed removed/renamed packet and registry APIs
  • focused distribution tests: 2 passing
  • affected native suite: 120 passing
  • ./gradlew clean check jar: 375 passing (255 ordinary + 120 native), zero failures/errors/skips
  • tested commit: 5949eff7fd34da290c8a02b7cc65a108b731cdc8
  • tested tree: 8f220bc1d088ca73abf597ee846043fd2aba0951
  • target base: 0fe6a14451a9d6a013c741125f4e7cf748649976
  • tracked-input aggregate SHA-256: 0fab246d61e0fc958c850d5681d401f2ee4e8b29efcc9b2a9bb54f3a57e69909

Publication effect

Merging to main triggers semantic release. Ticket completion remains blocked until current-head PR 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 or deployment change is included.

OpenProject: https://project.dmg.games/work_packages/403 ## Scope - build and test with Java 25 against Purpur API 26.3 build 2651 - pin native verification to the approved build 2651 URL and SHA-256 - adapt native packet and registry test boundaries to the 26.3 API - preserve runtime identity, metadata compatibility floor, behavior, and packaged exclusions - document the exact supported platform ## Verification - meaningful RED: 26.3 platform assertion failed against the old 26.2 build - meaningful native RED: 26.3 exposed removed/renamed packet and registry APIs - focused distribution tests: 2 passing - affected native suite: 120 passing - `./gradlew clean check jar`: 375 passing (255 ordinary + 120 native), zero failures/errors/skips - tested commit: `5949eff7fd34da290c8a02b7cc65a108b731cdc8` - tested tree: `8f220bc1d088ca73abf597ee846043fd2aba0951` - target base: `0fe6a14451a9d6a013c741125f4e7cf748649976` - tracked-input aggregate SHA-256: `0fab246d61e0fc958c850d5681d401f2ee4e8b29efcc9b2a9bb54f3a57e69909` ## Publication effect Merging to `main` triggers semantic release. Ticket completion remains blocked until current-head PR 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 or deployment change is included.
dmg added 1 commit 2026-10-16 23:51:20 +00:00
fix(base): support Purpur 26.3
CI / build (push) Successful in 2m8s
CI / build (pull_request) Successful in 2m11s
5949eff7fd
dmg merged commit ffecd38e99 into main 2026-10-16 23:53:41 +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-base#1