Skip to content

v0.5.1 (⚠️ BROKEN — client won't launch; use v0.4.0)

Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 23 Jul 04:05
8374280

⚠️ THIS RELEASE IS BROKEN — DO NOT USE. Use v0.4.0 (current recommended).
The client fails to launch: a Java split-package conflict — sodium-dynamic-lights
and ars-nouveau's bundled lambdynlights_api both export dev.lambdaurora.lambdynlights.api.
(The dedicated server is unaffected.) A fix is in progress and will NOT ship until it is
verified booting a live client + joining a server. Until then, use v0.4.0.


What's Changed

  • chore: post-release sync for v0.5.0 by @github-actions[bot] in #119
  • fix(build): make vppintegration actually compile (#67 real build) by @Guno327 in #117
  • fix(ci): live in-game progression audit for #61 (was offline, now selftest.js) by @Guno327 in #106
  • fix(client): remove sodium-options-api — v0.5.0 client-startup regression by @Guno327 in #121
  • fix(selftest): repair brace-merge error that broke KubeJS load (un-mints main) by @Guno327 in #125

Full Changelog: v0.5.0...v0.5.1

Test status (this mint)

  • Fast tier (ci.yml, run as part of this mint): unit tests
    (scripts/ci/tests) + all static checks (scripts/ci/run_all.py).
    PASSED (required before this release was built - see this run's
    own fast-tier job).
  • Boot tier (boot.yml, run as part of this mint): L0 boot smoke
    • L1 selftest - an actual resolved-mods dedicated-server boot plus a
      live /vpp_selftest run. PASSED (required before this release was
      built - see this run's own boot-tier job).
  • L2 HeadlessMC client smoke (scripts/tests/l2_client_smoke.py)
    did NOT run as part of this release. It is local-dev-sandbox-only
    per HANDOFF.md's "Release pipeline" section (needs a persistent
    HeadlessMC research instance + a local ~/.minecraft, neither of
    which exist on a hosted Actions runner). Rendering correctness, a
    live client join (L3), and multiplayer interaction remain unverified
    by this pipeline - see DESIGN.md's "Release engineering" section
    for the full L0-L3 boundary this project discloses on every release.