请求发布包含 0.17.4 之后修复的新稳定版 / Request a new stable release

Summary

Please consider cutting a new stable Weasel release incorporating the fixes merged after 0.17.4. The current stable installer failed in normal use on this machine, while the current official nightly is working.

Observed behavior and validation

• OS: Windows 11, build 26200.9445
• Failing version: Weasel 0.17.4.0 with librime 1.13.1
• Symptom: after selecting Weasel, keystrokes appeared as delayed Latin letters and the Chinese candidate window did not appear.
• Windows Event Viewer repeatedly recorded WeaselServer.exe crashing in rime.dll with exception 0xc0000005 at offset 0x16116.
• A clean reinstall of stable 0.17.4 did not resolve the failure.
• Working version: official nightly 0.17.4.50.d73f629.
• After upgrading and regenerating %APPDATA%\Rime\build\, deployment of five schemas completed, WeaselServer remained running without further crashes, and Chinese candidate selection plus committed Chinese text were manually verified.

A relevant fix appears to be #1789, which closed #1703 and was merged after the 0.17.4 stable release.

Important limitation

The nightly upgrade and regeneration of the generated build\ directory were performed in the same recovery sequence, so this observation does not isolate how much of the recovery came from the newer binaries versus rebuilding generated data. It does establish that the supported stable path remained broken after reinstall, whereas the current nightly plus a clean deployment works.

Request

1. Please consider a 0.17.5 (or next-version) stable release containing the post-0.17.4 fixes after maintainer QA.
2. Please include an upgrade test with an existing %APPDATA%\Rime\build\ directory. If generated data can be incompatible across bundled librime versions, automatically invalidate/rebuild it or document the required redeployment prominently.
3. Publish the signed official installer and a changelog through the normal release workflow.

I can help test a release candidate with clean install, upgrade from 0.17.4, preserved user configuration, reboot/login startup, and common Windows applications.

Start by reviewing fixes #1789 and #1703, then inspect the normal release workflow for the 0.17.4-to-next-version path. Test an upgrade with an existing %APPDATA%\Rime\build\ directory, clean deployment, reboot/login startup, and common Windows applications. Done means a signed stable installer and changelog are published, with generated-data handling documented or automated.