Changelog

Unreleased

0.2.1 - 2026-09-27

• Download and verify pinned upstream wstunnel release archives as part of the Gradle build.
• Verify native binary hashes and required licensing/provenance files inside the final Mod JAR.
• Pin the Gradle 8.9 distribution SHA-256 used by the checked-in wrapper.
• Add tag-driven GitHub Release, artifact attestation, checksums, and CurseForge publishing automation.
• Resolve CurseForge upload metadata within the correct game, loader, and client/server version types.
• Add a separate CurseForge artifact without bundled native executables while retaining the self-contained GitHub JAR.
• Require explicit COMMON-config consent before the CurseForge distribution can acquire pinned wstunnel 10.7.1 at runtime, with strict archive and executable SHA-256 verification and atomic installation.
• Add fail-closed acquisition, archive-safety, concurrency, cache, distribution-content, and descriptor tests.
• Rewrite current public descriptions around WebSocket gateways, managed ingress, private backends, and operator-provided edge capabilities, with a dedicated bilingual CurseForge usage guide.
• Publish the bundled JAR to GitHub Releases and only the native-free -curseforge.jar to CurseForge, retaining separate checksums and the exact CurseForge upload response.

0.2.0 - 2026-09-08

• Promote the standalone gateway, Discovery v1 routing, automatic endpoint detection, and optional ZstdNet 1.4.7/1.4.8 compatibility adapter into the 0.2.0 release line.
• Add repository-local Agent contribution instructions and dedicated user, development, and release-preparation guides.
• Document runtime log evidence for standalone mode, built-in gateway multiplexing, Discovery route selection, and detection of legacy fallback.
• Prepare the checked-in Gradle wrapper build and GitHub CLI workflow without logging in or publishing a release.

0.1.0-alpha.6

• Verify and enable the existing ZstdNet compatibility adapter for ZstdNet 1.4.8 while retaining 1.4.7 support.
• Add STANDALONE and EXTERNAL_PROXY deployment modes.
• Add a built-in plain-WS gateway that multiplexes Discovery and wstunnel on one public port.
• Generate the dedicated-server config in config/ and derive Minecraft target IP/port from server.properties.
• Auto-detect supported ZstdNet and publish the resolved runtime endpoints in generated/detected-server.toml.
• Make Discovery signing, WSS advertisement and persistent WSS downgrade enforcement optional and disabled by default.
• Add wstunnelTargetHost to Discovery routes so explicitly bound Minecraft servers work without manual client config.

0.1.0-alpha.5

• Compose ZstdNet's primary server-list UI path, which enters its connection hook with an existing loopback proxy and the bypass flag set.
• Recover the logical server address from ServerData, replace the premature direct proxy and clear the consumed ZstdNet bypass state.

0.1.0-alpha.4

• Fix ZstdNet composition on NeoForge by injecting directly into its optional connection hook.
• Stop depending on the undefined transformation order between ZstdNet's coremod and MiguelNetwork's mixins.

0.1.0-alpha.3

• Add signed MiguelNetwork Discovery Protocol v1 with dynamic per-server transport, public endpoint, path and target port.
• Persist Ed25519 server identity, client key pins, monotonic configuration epochs and a WSS downgrade floor.
• Add a loopback Discovery HTTP service designed for TLS/path multiplexing through Nginx.
• Compose ZstdNet 1.4.7 compressed streams with MiguelNetwork without modifying or reimplementing ZstdNet.
• Advertise separate ZstdNet and raw Minecraft routes and restrict wstunnel to both detected loopback targets.

0.1.0-alpha.2

• Remove client-side server allowlists and explicit WSS/WS selection from normal TOML configuration.
• Discover each endpoint as verified WSS, then WS, and fall back to unchanged vanilla TCP when neither probe succeeds.
• Use a protocol-fixed internal Minecraft target port and infer it from server-port on the server, so clients no longer configure or know the server's loopback port.
• Cache positive discoveries for the game process and retry negative TCP discoveries after 30 seconds.
• Add a protocol-compatible wstunnel WebSocket Upgrade probe and validate it against the live trusted-WSS endpoint.

0.1.0-alpha.1

• License MiguelNetwork under Apache-2.0 while retaining wstunnel's BSD-3-Clause notices.
• Record a preliminary license audit of wstunnel's locked Rust dependency closure.
• Add native NeoForge client and dedicated-server TOML configuration.
• Allow development runs to honor TOML values without forced enabled=false system-property overrides.
• Add opt-in client routing by exact host, endpoint, wildcard subdomain, or global wildcard.
• Keep independent, LRU-bounded sidecars for concurrent status Pings to multiple WSS endpoints.
• Separate client and server development game directories to avoid concurrent log-file contention.
• Infer the server tunnel target from the actual Minecraft listener when targetPort is zero.
• Add normal game/JVM shutdown cleanup for bundled wstunnel processes.
• Retain explicit, warning-heavy self-signed TLS switches for isolated development only.
• Add explicit plain WS transport for isolated tests and TLS-terminating reverse-proxy deployments; WSS remains the default.
• Document installation-time configuration and the completed end-to-end WSS validation.

0.0.1-tech-preview

• Embed official wstunnel v10.7.1 binaries for Windows x64 and Linux x64 with SHA-256 verification.
• Redirect the central Minecraft client connection path through a managed local wstunnel listener.
• Add a managed dedicated-server WSS listener with a fixed loopback-only restriction.
• Validate status Ping and two playable NeoForge sessions over local WSS.