Skip to content

Remold v0.2.2

Choose a tag to compare

@github-actions github-actions released this 05 Nov 11:09
· 547 commits to main since this release

Remold v0.2.2 Release Notes

v0.2.2 focuses on the Gradle binary plugin, Fabric/Mixin hot-swap correctness, and on making
hot-swap failures observable instead of silent.


Highlights

  1. Binary Gradle plugin + Plugin Portal

    • New :gradle-plugin binary plugin (io.github.i-hope1.remold) with a type-safe RemoldExtension
      DSL and configuration-cache support.
    • The root remold.gradle / remold.gradle.kts scripts are now thin shims over the binary plugin
      (previously two parallel implementations).
    • Mod templates migrated to JitPack binary-plugin resolution; English plugin docs added for the
      Gradle Plugin Portal review.
  2. Fabric / Mixin hot-swap correctness

    • @Unique field add/remove is supported during Fabric hot-swap.
    • Target class bytecode is resolved from the source cache / watch dirs, and duplicated Loom VM args
      are removed.
    • A layout-prediction copy (ephemeral class loader) can no longer become the hot-swap target.
      Before this fix, every round redefined a never-initialized copy: the log still said
      HotSwap successful, but InitFix skipped the class (not initialized) and @OnReload never fired.
    • Stale same-mod jars in run/mods are quarantined (renamed to .jar.remold-disabled) instead of
      only warning, preventing the loader from silently running old bytes.
  3. Failures are surfaced

    • Post-processing failures (InitFix patches, @OnReload, cache eviction) are no longer swallowed by
      the scheduler's Future; the entry point catches Throwable and reports it.
    • Redundant dynamic redefines are skipped when the runtime bytecode is unchanged.

Fixed

  • Layout-prediction copy stealing the hot-swap target ("field added but never applied").
  • Silent post-processing failures after redefineClasses.
  • @Unique field add/remove during Fabric hot-swap.
  • Mixin target bytecode resolution from source cache / watch dirs; duplicated Loom VM args.
  • out/production vs build/classes conflict via buildMode and timestamp arbitration.
  • Loom run-config generation (Make-based configs, IDEA build auto-detection from gradle.xml).
  • Release packaging: pick the binary Gradle plugin jar (not the javadoc jar); skip example remold
    integration when the local plugin jar is absent.

Added

  • :plugin-fabric module (remold-plugin-fabric.jar): loader integration (class path groups, stale-jar
    inspection, mods watch exclusion) moved out of core into the generic HotswapPlugin windows
    (onPremain, onWatchPathsChanged, isWatchPathIgnored).
  • RemoldAgent split: layout decision, removed-member scanning, watch-path registry, watcher thread,
    jar extraction and environment probing extracted into dedicated modules; public API unchanged.
  • HotswapPlugin gained three default methods; PluginWatchPathTest locks down "no loader-specific
    rules in core / plugin votes are honored / a throwing plugin does not break path decisions".
  • Kotlin DSL modernization and Javadoc/jump-link cleanups across all mod templates.

Verification

  • CI: full test matrix (javac 8/11/17/21/25), DCEVM (JBR 21) live tests, and P0.5 probes on JBR 17/21.

Full Changelog: v0.2.1...v0.2.2