Changelog ​

September 28, 2026 ​

• Connect plugin Upgrade A tunneled Spigot login that stalls before Connect now names where it stopped. A packet-level login plugin can consume LOGIN_START before connect_data_handler, so Connect's offline-login cycle never runs and the client waits without a login response; before 0.15.16 the connector recorded no cause, leaving only the backend's later, cause-blind login timeout. 0.15.16 installs a watchdog before the consuming handler: ten seconds after the handshake it writes exactly one warning with the player, session, endpoint and packet count, names the probable packet-pipeline cause, and explains why a passthrough connect-player exemption is not a fix. This is attribution only — it does not kick the player, fabricate a packet, complete the login or change a healthy session.

September 27, 2026 ​

• Connect plugin Upgrade Chat from a tunneled player no longer kills the session on current Paper/Spigot backends. Connect's Spigot chat filter rebuilds each serverbound chat packet to strip its unsigned-chat component, and it resolved the replacement constructor by hard-coded parameter types, while backends from 1.21.5 on — the Minecraft 26.3 line included — carry Optional<MessageSignature>. The lookup threw inside the injected pipeline for every plain chat message, and because the filter only ever sees post-login traffic no login failed: the connection closed right after spawn and the failure surfaced as a generic internal-server exception with no plugin-log line, so a session on 0.15.14 or earlier that dies this way reads as an unexplained teardown. 0.15.15 resolves the constructor from the runtime value the packet exposes, so one path serves the raw and the Optional shape, and a shape nothing matches now names the missing accessor and the types observed instead of a bare reflection error. It is one deterministic defect on that path, not an explanation for every post-spawn closure reported on current backends. 0.15.14 changes only the release pipeline (one apostrophe in a merged commit subject no longer stalls the release-please auto-merge), so it adds no plugin behaviour of its own; install 0.15.15, which contains the fix.
• Gate Upgrade A backend packet Gate cannot decode now names the packet that closed the connection. When a backend sent a packet Gate recognised but could not decode, Gate silently closed the backend socket at default verbosity, the backend logged nothing and the player saw only Internal server connection error; on a Connect tunnel there was nowhere else to attribute the close. v0.74.28 writes one error on that backend-side close with the peer, packet type, packet ID and protocol. It is observability only: unknown or malformed client-side traffic stays quiet so an untrusted client cannot turn the diagnostic into a log-flood primitive.
• GeyserLite Upgrade GeyserLite accepts the current Bedrock clients again, and a native GeyserLite loads its own config. v0.5.28 carries the upstream Geyser revision that registers Bedrock 26.50/26.51 — every GeyserLite up to v0.5.27 stops at Bedrock 26.45, which made GeyserLite, the Connect edge and any Gate bedrock: true listener built on it reject every current Bedrock client — but v0.5.28 published no downloadable build, so do not pin it. v0.5.29 registers the config classes Geyser's annotation processor generates, which the native-image build was dropping: without them every Geyser config load failed, presenting as a restart loop in standalone/subprocess mode and as a silent exit when embedded. v0.5.30 raises the purego dependency and v0.5.31 changes only the release pipeline. Install v0.5.31, which contains them all with builds attached.
• Gate Upgrade Stopping or reloading Gate no longer leaves a Connect runtime behind. v0.74.19 stops and joins the Connect runtime Gate started, both on shutdown and before a config reload replaces it; previously the superseded runtime was swapped out without being stopped, so two connectors could watch the same endpoint and write the same token file, and Gate reported itself stopped while that runtime was still running. v0.74.20 refuses to start a runtime once Gate has been asked to stop, and v0.74.21 runs Gate's event manager on a race-free wrapper — the manager Gate used could silently drop a config update when a delivery overlapped a sibling subscriber's unsubscribe, with no log line at all. Install v0.74.21.
• Gate Upgrade A Windows editor or deploy tool can save Gate's config while Gate is reading it. Gate opened its config with a handle that shares read and write but not delete, so an editor's or deploy tool's atomic ReplaceFileW save of gate.yml was refused with ERROR_SHARING_VIOLATION for as long as one of Gate's own reads was in flight — on Windows, 1208 of 3000 replacements failed on that read path and none on the delete-sharing handle Gate already used for fingerprints. v0.74.26 reads the config content with the delete-sharing handle, and v0.74.27 covers the discovered config.yml path, which viper read on its own. Install v0.74.27, which contains both.
• Gate Upgrade Gate names the runtime that died, the backend that never answered, and the version it actually resolved. v0.74.12 logs the ViaLite runtime Gate resolved at startup — version, how it was resolved (download, cache, pin, explicit path) and where it runs from — so the live translation build is readable instead of inferred from the runtime's own output. v0.74.18 reports a managed ViaLite runtime that exits after startup: one error naming the component, the resolved version and the backends that runtime owned, and joins then fail saying protocol translation is down instead of the runtime module's bare server not started, which reads like a configuration mistake. v0.74.23 bounds and names the bridge dial of a dynamic, tunnel-backed backend the translation bridge cannot reach — that dial is detached from the join's deadline on purpose, so a stalled backend blocked the join forever and ended as a generic closed-connection message with nothing naming the backend. Install v0.74.23.
• Gate Upgrade A hung Gate now tells you how to get a stack dump. kill -QUIT is listed in Gate's termination signals, so os/signal consumes it: Gate shuts down gracefully and prints zero goroutine lines — following the usual advice ends the run and returns nothing. v0.74.25 prints the working instruction (kill -ABRT <pid>, which also ends the run, so capture the console first) on the graceful-shutdown line, and a new troubleshooting page gives the signal table, what the dump looks like, and why neither net/http/pprof nor a debugger is an alternative on a release build.

September 26, 2026 ​

• Gate Upgrade A Bedrock port conflict no longer costs ten minutes and your Java players. With managed Bedrock enabled on a host where another process already holds the Bedrock UDP port, the managed runtime could never bind: Gate waited the full ten-minute startup timeout, the public Bedrock listener never answered, and Gate then shut the proxy down and disconnected every Java player with it — a Bedrock-only misconfiguration taking down Java. v0.74.16 reports the held port within seconds and fails fast, so it is a startup error instead of a silently degraded proxy.

September 21, 2026 ​

• Gate Upgrade Gate reads ports as the unsigned 16-bit values they are. The handshake port is unsigned on the wire and Gate decoded it as signed, so a client declaring a port of 32768 or more arrived as a negative number — and that value is not merely logged, it is formatted into the virtual host the connection routes on, so 65535 became the host host:-1. v0.74.7 decodes it unsigned, v0.74.9 rejects an out-of-range port with an error instead of silently wrapping it into a different port that was never in the address (host:70000 became 4464, and host:65536 was accepted as the no-port sentinel), and v0.74.10 writes BungeeCord's ServerIP port as the unsigned value it is. Install v0.74.10, which contains all three.
• Gate Upgrade Gate's login RSA key size is configurable. auth.privateKeyBits in config.yml now sets the key Gate generates for the Java login handshake. Before v0.74.8 the option existed, was documented and was never read, so every gate generated a fresh 1024-bit key at startup with no way to raise it from configuration — and the login packet decoders capped the key fields at exactly one 1024-bit block, so a larger key could not have completed a login at all. The default stays 1024 bits; install v0.74.8 to set your own.

September 19, 2026 ​

• Gate Upgrade Gate's vulnerable dependency set is refreshed. v0.74.1 bumps every manifest and lockfile that pinned a version with an open Dependabot advisory — 51 alerts, 13 of them high, none against Gate's own code. The part that ships inside the proxy binary is go.mod: grpc 1.82.1 to 1.84.0, x/net 0.53.0 to 0.59.0 (CVE-2026-25680), x/image 0.18.0 to 0.46.0, and the OTLP exporters 1.38.0 to 1.46.0. The docs site and API-example lockfiles are refreshed in the same release.

September 18, 2026 ​

• Gate Upgrade Gate knows Minecraft 26.3. v0.74.0 adds 26.3 (protocol 777) to Gate's version table and fails closed on a protocol it does not know. Before it, an unknown protocol fell through to the minimum-version packet registry: a 26.3 login was encoded with pre-1.8 rules, the client failed to decode minecraft:hello, and the version check accepted every numeric protocol because it only rejected the unknown sentinel. Anyone running their own Gate in front of current Java clients needs this release.

September 14, 2026 ​

• Connect plugin Upgrade Endpoint auth failures on an organization-owned endpoint now name the real problem instead of telling you to switch organizations. Connect 0.15.12 reports the actual condition — the connector token does not match the token stored for that endpoint name — and the fix (put the new token byte-for-byte into the connector token file, token.json or CONNECT_TOKEN, not config.yml, then restart), instead of blaming the Minekube organization; the endpoint/token mismatch error gained the same guidance. 0.15.13 changes only the release pipeline (it retries a Modrinth read-back), so it adds no plugin behaviour of its own; install 0.15.13, which contains the 0.15.12 fix.

September 13, 2026 ​

• Gate Upgrade Reserved names stay blocked for offline players arriving through Connect, even when the proxy runs onlineMode: true. Gate v0.71.16 blocks unsafe offline usernames, v0.73.0 scopes the offline username blacklist to Connect so direct-listener setups keep their own policy, and v0.73.13 fixes the case reported from a public endpoint, where an offline identity completed login under a reserved premium name with no kick — the check now reads whether the player is authenticated, not only the proxy's online-mode setting. Install v0.73.13.
• Gate Upgrade Players joining through a premium Connect tunnel keep their authenticated identity, and their login no longer hangs. v0.73.12 stops Gate's accepted-connection wrappers from hiding the identity Connect had already authenticated, which made Gate treat the player as unauthenticated and send a Java EncryptionRequest into the tunnel.

September 10, 2026 ​

• GeyserLite Upgrade GeyserLite keeps up with current Bedrock clients. v0.5.22, v0.5.26 and v0.5.27 each carry a new upstream Geyser revision (Gate v0.73.10 bundles v0.5.27); install v0.5.27, which contains them all with builds attached. v0.5.23 and v0.5.24 repaired the release pipeline that had published some releases without downloadable assets, and v0.5.25 shipped without builds — do not pin it.

September 4, 2026 ​

• Gate Upgrade Gate stops running with a dead Bedrock listener. v0.72.6 surfaces unexpected managed GeyserLite exits and bridge-listener failures from the Bedrock runtime, so Gate and Moxy exit and their supervisor can restart them, instead of keeping healthy Java and HTTP health endpoints while the public Bedrock listener is gone; config reloads fail closed rather than leaving Bedrock absent.

September 3, 2026 ​

• Connect plugin Upgrade Configs without a Bedrock-identity section get safe defaults, and an existing config.yml loads again on Velocity. 0.15.10 fills the missing Bedrock-identity section with safe Minekube metadata defaults and warns the operator while leaving explicit sections — including quoted YAML keys — untouched; 0.15.11 fixes a crash 0.15.10 introduced on Velocity, where having any config.yml failed the load with a misleading "delete the config file" message. Install 0.15.11, which contains both; do not pin 0.15.10 on Velocity.

August 24, 2026 ​

• Connect plugin Upgrade Bedrock identity handling is safer on multi-injector servers and survives plugin reloads. Connect 0.15.4 scopes Bedrock principal admission to Bedrock connections, 0.15.6 recovers the admission coordinator after a plugin reload instead of dropping Bedrock joins, 0.15.8 shares one coordinator across all injectors, and 0.15.9 applies an interim default that generates a version-0 Bedrock principal with a warning until the next identity producer ships. Install 0.15.9.
• GeyserLite Upgrade GeyserLite tracks current Bedrock clients again through a long chain of upstream compatibility updates. Releases v0.5.3 through v0.5.21 (August 9–24) pull in repeated Geyser protocol updates; install v0.5.21, which contains them all with builds attached. Several intermediate releases were published without downloadable builds and should not be pinned.
• GeyserLite Upgrade Player skins decode without AWT, which unblocks the native-image builds. v0.5.10 decodes skins without AWT, and v0.5.21 removes AWT from the skin provider's class initialization so native releases can ship again; install v0.5.21.

August 22, 2026 ​

• Craftless Upgrade Craftless CLI and daemon fixes in v0.3.7: the CLI preserves schema-defined string request fields, the daemon runs the newest packaged client lane inside Docker, and latest-Fabric canary failures now report the actionable cause instead of a bare failure.

August 21, 2026 ​

• Connect plugin Upgrade Session proposals report the real rejection reason, and endpoints without an org are admitted under Bedrock identity enforcement. Connect 0.15.7 logs the exception message when a session proposal is rejected and admits org-less endpoints; 0.15.5 preserves tunnel delivery and late wrappers. Install 0.15.9, which contains both.

August 17, 2026 ​

• Gate Upgrade Gate applies the linked Floodgate Java identity on its direct listener. v0.71.3 fixes Bedrock players with a linked Java account joining through Gate's direct listener, and v0.71.2 also updates Gate's bundled GeyserLite to v0.5.11; install v0.71.3, which contains both.

August 8, 2026 ​

• Connect plugin Upgrade Managed Bedrock identity is now zero-config and understands Connect's signed principal v2. Releases 0.14.0 and 0.15.0 added generated verifier defaults and the newer identity protocol; 0.15.1 then isolated stale Watch proposals but was superseded after its release assets changed during a retry. Install 0.15.3, which contains all three changes with stable published artifacts.
• Connect plugin Upgrade Login plugins can cooperate with Connect without hanging authenticated players or replacing their skin data. Connect 0.13.0 published a stable connect-player channel marker and 0.13.1 re-asserted Connect's login decision after premium-autologin plugins; install 0.15.3, which contains both changes. The login-plugin guide documents the remaining ordering limits.
• Connect plugin Upgrade Spigot now reports useful diagnostics when a server update changes the internal mappings Connect needs. Added in 0.12.7 and included in 0.15.3.

August 7, 2026 ​

• Gate Upgrade Current Bedrock clients can join Gate again, and Connect-routed Bedrock identity uses the frozen signed-principal protocol without logging raw identities. Upgrade to Gate v0.71.1, which contains the identity work from v0.71.0 and the current-client compatibility fix.
• GeyserLite Upgrade GeyserLite exposes verified Bedrock ingress to embedded and subprocess consumers and includes the latest upstream Bedrock compatibility fixes. The authenticated ingress API shipped in v0.5.0 and the upstream compatibility updates followed in v0.5.1 and v0.5.2; install v0.5.2.

August 4, 2026 ​

• Connect Live Every Connect endpoint now accepts Microsoft/Xbox-authenticated Bedrock players without requiring a linked Java account by default. An authoritative link still preserves the linked Java identity; an unlinked player receives a stable native Bedrock/XUID-derived identity. Offline/cracked Bedrock remains unsupported, and cracked Java remains a separate endpoint opt-in. Deployed across the hosted Connect service on August 4. (Internal repository, no public link.)

July 26, 2026 ​

• Connect Live Minecraft 26.2 players can join the Minekube hub again. They could not join between June 16 and July 26: the hub backend was still running a 26.1 protocol build while the edge accepted 26.2 connections. Server-list pings kept looking healthy throughout, because the Connect edge answers pings itself. Fixed and deployed on July 26. (Internal repository, no public link.)
• Gate Upgrade Gate v0.68.31 contains a security fix for PROXY-protocol handling. If you expose Gate directly, upgrade to v0.68.31.
• Gate Upgrade Three separate bugs that broke modded servers are fixed in Gate v0.68.30: large mod registry payloads over 1 MiB no longer kill the connection, Forge clients no longer lose their hostname when routed through a second proxy, and Gate Lite now warns you when it is ignoring forwarding, onlineMode or servers settings instead of silently accepting them.
• Gate Upgrade Gate v0.68.30 updates its bundled GeyserLite to v0.4.9. Gate shipped GeyserLite v0.3.17 from June 30 to July 26 while GeyserLite itself reached v0.4.9, so self-hosted Gate carried a stale Bedrock runtime for that period.
• Gate Did not work Managed GeyserLite for self-hosted Gate Lite did not start, and as at July 26 the underlying startup failure was still open. It could not complete its Minecraft data download, so no Bedrock listener came up. It was changed on July 26 to fail immediately with an error telling you to point it at a prebuilt GeyserLite binary, instead of hanging your proxy startup for ten minutes with no explanation. (Internal repository, no public link.)
• Connect Live Bedrock players with a Microsoft/Xbox account but no linked Java account can now be admitted to a Connect endpoint. As shipped on July 26, it was off by default and enabled per endpoint by Minekube on request; refused joins reported a reason instead of timing out with a bare network error. The policy later became the default for every endpoint on August 4. (Internal repository, no public link.)
• Connect Live Connect endpoint status pings could stop resolving on a proxy machine after a network interruption and stay broken until that machine restarted. Fixed and deployed on July 26. (Internal repository, no public link.)
• Connect Live A Connect endpoint could keep reporting healthy while no player joins reached it. The dashboard, heartbeat and tunnel all showed the endpoint as active, but every join failed with an internal connection error, once that machine's internal message transport had reached a permanently closed state. A machine in that state now releases its endpoint session, so your connector moves to a healthy one. Fixed and deployed on July 26. (Internal repository, no public link.)
• Connect plugin Upgrade The Connect plugin supports ViaVersion 5.x legacy initializer unwrapping on Spigot in 0.12.4.

July 25, 2026 ​

• Gate Upgrade Gate v0.68.29 updates its bundled gRPC library to a release carrying an upstream security fix. If you self-host Gate, upgrade. This is a separate change from the PROXY-protocol security fix in v0.68.31; Gate v0.68.31 and later contain both.

July 24, 2026 ​

• Connect plugin Upgrade The Connect plugin failed to load. It failed to load on Paper (0.12.0), failed to start its endpoint on Spigot/Purpur (0.12.1), and failed to load at all on Velocity 4.0.0 (0.12.2). All three were regressions introduced in 0.12.0 and are fixed in 0.12.3; update to 0.12.4.
• Gate Upgrade Chat and commands were being rejected on Minecraft 1.20.5+ clients connecting through Gate, with Last seen update ignored previously acknowledged message at index N. Direct connections were unaffected. Fixed in v0.68.28.

July 19, 2026 ​

• Gate Upgrade Gate Lite status handling (v0.68.27): cached status responses keep their full expiry window, stale Via bridge requests are skipped on retry, and status-response failures are now logged instead of failing silently.

July 15, 2026 ​

• Connect plugin Upgrade The Connect plugin can verify the signed Bedrock identity that Connect attaches to a Bedrock session. Verification is off by default with warn and require modes, sessions with a missing or invalid identity are rejected once you turn it on, verifier keys can be pinned directly or fetched from a metadata URL, and trusted Bedrock sessions are recognised. Built across 0.8.0, 0.9.0, 0.10.0 and 0.12.0. You need a current public key from Minekube before enabling it.

July 13, 2026 ​

• GeyserLite Upgrade GeyserLite can trace Bedrock packets for debugging, off by default, in v0.4.0.

July 12, 2026 ​

• Connect plugin Upgrade The Connect plugin exposes a health endpoint for its Connect watcher, so monitoring can check it directly, in 0.11.0.

July 7, 2026 ​

• Connect Live Connect reliability work through June and early July: browser-hub fallback after endpoint kicks, endpoint sessions kept during server switches, authorized transfers while the current server is unavailable, cached endpoint status pings, and custom-domain routes loaded before serving. (Internal repository, no public link.)
• Craftless Upgrade Stopping an official Fabric client now actually terminates it. It previously reported success while leaving the Minecraft process running. The CLI installer also now includes the latest official lane. Both were tagged v0.3.5, which was published with no downloadable build; install v0.3.6 instead, which contains both fixes and has builds attached.

July 4, 2026 ​

• Connect plugin Upgrade The Connect plugin's token error message now points at the token file you need to fix in 0.7.11.

July 2, 2026 ​

• Gate Upgrade Config plugin messages are queued during backend login instead of dropped (v0.68.22).
• Connect plugin Upgrade The Connect plugin explains why Connect rejected its credentials instead of reporting a bare authentication failure, in 0.7.10.
• Craftless Upgrade Three Craftless CLI and daemon fixes, tagged v0.3.1 — a release that has no downloadable build and cannot be repaired, so install v0.3.6, which contains them: the CLI defaults the daemon workspace instead of requiring one, ambiguous API help lists every matching method, and the daemon reports connection attempts it never observed.

July 1, 2026 ​

• Connect Live Opening a Connect endpoint tunnel could fail before the request ever reached Connect. When the machine that received the request was not the machine holding your endpoint's session, the request was rejected upstream instead of being handed over, so tunnels and the joins that depend on them failed while the endpoint itself looked healthy. Those requests are now passed directly to the machine holding the session. Fixed and deployed on July 1. (Internal repository, no public link.)
• Craftless Upgrade Craftless reports which Fabric runtimes it supports and refuses targets it cannot run. Fabric runtime and loader support targets are exposed in the loader matrix, unsupported or undiscovered targets are rejected with a structured error, and a headless launch that cannot be satisfied now stops immediately instead of starting. All were tagged v0.3.0, a release that has no downloadable build and cannot be repaired; install v0.3.6, which contains them.

June 30, 2026 ​

• Connect plugin Upgrade The Connect plugin's websocket tunnel connections now reach the machine that holds your endpoint session. When the tunnel address named a specific machine, the plugin did not pass that along, so the connection could land elsewhere and fail. Fixed in 0.7.9.

June 29, 2026 ​

• Connect plugin Upgrade The Connect plugin's peer-to-peer networking no longer shares Netty internals with your server, removing a class of interference between the two, and Velocity chat sessions now survive the reconfiguration step during a Connect tunnel join. Both in 0.7.8.
• Craftless Upgrade Craftless gets a documentation site, version discovery and a screenshot API. v0.2.0 publishes the docs site, reports which runtime versions it can run and defaults to the latest, adds an API for generated screenshot artifacts, and routes every CLI invocation through that API instead of a second code path; that release has no downloadable build and cannot be repaired, so install v0.3.6, which contains all of it. Earlier the same day, v0.1.2 added latest-release and latest-snapshot as Minecraft version aliases, a --loader-version option when creating a client, and --help for each command group.

June 28, 2026 ​

• Craftless Upgrade Craftless finds and picks a Java runtime for you. craftless runtimes java list reports the runtimes it discovered on your PATH, craftless runtimes java resolve --mc <version> tells you which one it would use for a given Minecraft version, and the choice is recorded in the workspace cache so launches stay repeatable. In v0.1.1.

June 26, 2026 ​

• Gate Upgrade Gate adopts modern Common text components, modernising text rendering across Gate (v0.68.2).
• Craftless Upgrade Craftless is public. v0.1.0 is the first public release of our Minecraft client automation framework. It launches or attaches to real Minecraft Java clients — headless for unattended runs, or with the game window visible so you can watch — and exposes each running client as a generated local OpenAPI document, so agents, tools and CI drive the real client without a hand-maintained catalogue of gameplay commands. Ships as an install script for Linux and macOS, a runtime container image, and a GitHub Actions setup action.

June 23, 2026 ​

• Gate Upgrade Gate can route dynamic servers through a managed Via runtime (v0.68.0), using the ViaLite auto-latest subprocess runtime (v0.67.0). From v0.68.14 Gate also skips ViaLite when the backend protocol already matches. ViaLite v0.3.0 supports embedded dynamic backends.

June 22, 2026 ​

• Gate Upgrade Keepalive handling is stabilised across server switches and transitions — players were being timed out during transfers. Fixed across releases up to v0.66.36.
• GeyserLite Upgrade GeyserLite could crash during Bedrock network cleanup. The released native builds were missing a runtime option their networking layer needs, so cleanup could kill the process with an unsupported-feature error. Fixed in v0.3.14.

June 21, 2026 ​

• Connect plugin Upgrade The Connect plugin no longer disconnects chat on newer Paper builds (NoSuchMethodException: LastSeenMessages.<init>), fixed in 0.7.7.
• GeyserLite Upgrade GeyserLite's native builds failed from June 18 to June 21, and again in July. Releases published without downloadable builds should not be pinned; whether a given release has them is shown on its release page, which is where to check before you pin a version. Separately, signing changed at v0.3.10: one .sigstore.json bundle per artifact replaced the separate .sig files.

June 17, 2026 ​

• Gate Upgrade Gate installs on musl-based Linux (Alpine) (v0.66.27).

June 13, 2026 ​

• Connect plugin Upgrade The Connect plugin works on newer Velocity and Netty builds again. Connect's tunnel channels and Velocity's backend channels were running on incompatible event-loop models; 0.7.6 bridges them.

June 8, 2026 ​

• Gate Upgrade Gate's arm64 image could not start managed Bedrock support. It downloaded GeyserLite and then exited immediately, because the image was missing a library the downloaded executable needs; read-only containers reported a misleading "binary not found" instead, because there was nowhere to write the download. v0.66.7 adds the missing library and a writable cache location for downloaded components.
• GeyserLite Upgrade The published arm64 container image could not run GeyserLite, and failed downloads were reported as a missing binary. The arm64 image lacked the C runtime the executable needs, and the locator discarded the real reason a download failed — an unsupported platform, a read-only cache, a network error — reporting only that no binary was found. Both fixed in v0.2.7.
• GeyserLite Upgrade GeyserLite runs on Windows. v0.3.0 publishes a Windows amd64 executable that the Go and Rust integrations can download automatically. Windows uses the separate-process mode; the embedded-library mode is Linux-only in this release.

June 5, 2026 ​

• GeyserLite Upgrade GeyserLite's default network memory limit was too small for Bedrock chunk bursts. The default cap on its off-heap networking buffers rises from 16 MB to 64 MB in v0.2.5, and the tuning guide's suggested limits for busy servers rise with it. If you set that limit yourself, review it.

June 4, 2026 ​

• Gate Upgrade Gate's Docker images use glibc base images so the binary actually executes (v0.66.5).