gproxy v4.1.12

v4.1.12

A first-run setup wizard for the CLI, matching the application's, with channel and credential setup in both; reproducible F-Droid builds again; and a per-user data directory for WinGet installs.

CLI 新增与 Application 一致的首次设置向导，两者都可在设置时选择渠道并添加凭据；恢复 F-Droid 可复现构建；WinGet 安装改用按用户的数据目录。

English

Added

• Running gproxy in a terminal for the first time now starts a setup wizard instead of printing generated credentials: language, listening address, data directory and database, administrator, the channels you plan to use, and a credential for each new provider (API key or sign-in), or a configuration export to import. Answers are saved to ./.env with a newly generated master key, and the wizard ends with the base URL, the gateway API key and an offer to install a background service. Containers, service managers and redirected input keep the previous behaviour. See Bootstrap.
• The application's setup wizard has the same channel step: pick channels to create providers for, or import a configuration as before, then add credentials before the console opens.

Fixed

• Fix the F-Droid build of v4.1.11 not reproducing the published APK. The release image had moved to newer Rust, Go and Node versions while the F-Droid recipe kept the old ones, so the native library differed. Both builds now install Rust 1.99.1, Go 1.27.2, Node.js 24.22.1, Gradle and pnpm from one pinned script.
• Fix the CLI and headless CLI installed with WinGet failing to start outside a writable directory, for example from the Start menu or the WinGet validator. Like a Microsoft Store install, a WinGet install now defaults its data directory to %LOCALAPPDATA%\GPROXY when --data-dir / GPROXY_DATA_DIR is not set; a ZIP unpacked by hand still uses ./data. If you ran a WinGet-installed gproxy from a directory holding data, pass --data-dir <that folder> or move it to %LOCALAPPDATA%\GPROXY.

Changed

• install.ps1 and the Microsoft Store listing now use the same Windows data directory as the binary, %LOCALAPPDATA%\GPROXY. Windows paths are case-insensitive, so existing install.ps1 instances keep their data.

简体中文

新增

• 在终端中首次运行 gproxy 时会进入设置向导，不再直接打印生成的凭据。向导依次设置语言、监听地址、数据目录和数据库、管理员账户、打算使用的渠道，并为每个新供应商添加凭据（API Key 或登录），也可以改为导入一份配置导出文件。答案连同新生成的主密钥保存到 ./.env，最后显示 Base URL 和网关 API Key，并可选择安装为后台服务。容器、服务管理器和重定向输入保持原有行为。详见首次初始化。
• Application 的设置向导增加同样的渠道步骤：可选择渠道创建供应商，或像以前一样导入配置，并在进入控制台前添加凭据。

修复

• 修复 v4.1.11 的 F-Droid 构建无法复现已发布 APK 的问题。发布镜像已升级到较新的 Rust、Go 和 Node 版本，而 F-Droid 构建仍使用旧版本，导致原生库不一致。现在两者都通过同一个固定版本的脚本安装 Rust 1.99.1、Go 1.27.2、Node.js 24.22.1、Gradle 和 pnpm。
• 修复通过 WinGet 安装的 CLI 和 Headless CLI 在不可写目录下无法启动的问题，例如从开始菜单启动或 WinGet 验证时。与 Microsoft Store 安装一样，WinGet 安装在未设置 --data-dir / GPROXY_DATA_DIR 时，默认数据目录改为 %LOCALAPPDATA%\GPROXY；手动解压的 ZIP 仍使用 ./data。如果你之前在某个含有 data 文件夹的目录下运行 WinGet 安装的 gproxy，请通过 --data-dir <该文件夹> 指定，或将其移动到 %LOCALAPPDATA%\GPROXY。

调整

• install.ps1 和 Microsoft Store 商店说明改用与程序一致的 Windows 数据目录 %LOCALAPPDATA%\GPROXY。Windows 路径不区分大小写，已通过 install.ps1 安装的实例数据不受影响。

Built once by GitHub Actions. CLI (gproxy-*) and Application (gproxy-tauri-*) packages are separate.