You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(platforms): make multi-platform builds work on latest MC versions
When Paper publishes a new calendar-versioned release (e.g. 26.1.2)
pluggy init defaults to it, but the downstream platform providers
weren't ready: sponge resolved spongeapi to a version only published as
-SNAPSHOT on Maven, and folia still hardcoded the old <mc>-R0.1-SNAPSHOT
artifact name even though folia-api moved to the build-stamped form
(26.1.2.build.8-stable) like paper did. Both now probe maven-metadata
and pick a published variant.
Also surfaced while testing: build output displayed absolute paths, and
--platform bungeecord was rejected even though that's the natural name
for the waterfall-backed proxy.
- sponge: resolvePublishedApiVersion checks the spongeapi metadata for
a release variant before falling back to -SNAPSHOT.
- folia/paper: share papermc.resolveApiVersion, which prefers the
highest <mc>.build.<N>-<channel> entry and falls back to the SNAPSHOT
form on miss.
- build: print outputPath relative to the cwd pluggy was invoked from
(paper/bin/foo.jar instead of /Users/.../paper/bin/foo.jar); absolute
path retained when --output points outside cwd and in the JSON
payload.
- platforms: new resolve()/aliases() on the registry; parsePlatform
resolves aliases (bungee, bungeecord -> waterfall).
0 commit comments