Release gproxy v3.0.2 · LeenHawk/gproxy

v3.0.2

Deleting a route, provider, organization, user or quota now takes everything it owns.

Deleting a route removes its members and the public model names mapped to it; a deleted route no longer keeps a name taken (#219).
Every table now declares what it owns, and each delete runs as one generated transaction: a provider takes its credentials, route members, aliases, catalogue entries, pricing rules, routing rules and rule-set attachments; a price rule takes its rates; a quota takes its windows and settlements; an organization, team, user or key takes the permissions, rate limits and quotas scoped to it; a user also takes their keys, sessions and OAuth grants; deleting a team leaves its users without a team. History rows keep their references.
A schema step sweeps rows whose owner is already gone, so orphans left by earlier versions disappear on first start, and a test refuses any reference column that is neither owned nor listed as history.
Retention pruning also removes the quota-tracking rows that pruned usage rows owned, and stale quota activity, which previously grew without bound.

Release executables are packed with UPX 4.2.4 again: UPX 5.x turned the x86_64 Linux executable into one that crashes at startup.
A route member names a provider and an upstream model; the per-member credential pin, which v2 never had, is gone. Members that had pinned a credential now use the provider's credential pool like every other member.

删除负载均衡路由会连带删除它的成员和映射到它的公开模型名，被删路由不再占着名字（#219）。
每张表都声明自己拥有哪些行，所有删除作为一个生成的事务执行：删除 Provider 带走凭证、路由成员、别名、模型目录、价格规则、路由规则和规则集挂载；删除价格规则带走费率；删除配额带走窗口和结算；删除组织、团队、用户或密钥带走作用于它们的权限、限流和配额；删除用户还会带走密钥、会话和 OAuth 授权；删除团队只把用户的团队置空。历史记录保留引用。
一个 schema 步骤会清理归属方已经不存在的行，旧版本留下的孤儿在首次启动时消失；并有测试拒绝任何既未声明归属也未列为历史的引用列。
保留期清理同时删除被清理用量行拥有的配额跟踪行和过期的配额活动记录，之前它们会无限增长。

发布的可执行文件改回用 UPX 4.2.4 压缩：UPX 5.x 压出来的 x86_64 Linux 可执行文件启动即崩溃。
负载均衡成员只指定 Provider 和上游模型；v2 从未有过的"按成员指定凭证"已移除。之前指定了凭证的成员现在和其他成员一样使用 Provider 的凭证池。