Repository navigation
feat(ai): add shared group key authorization - #36
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
群組觸發提醒現在可使用持有人明確授權的一組既有 Key。管理員先在群組
/ai group allow,持有人點「授權我的 Key」進入 Bot 私聊,以按鈕選擇自己的既有 Key,最後由管理員/ai group on啟用;不必手填群組 ID 或 Key ID。驗證:本機
make check(使用現有虛擬環境,UV_NO_SYNC=1)通過,包含 Ruff、426 個 unit tests 與 smoke flow;git diff --check通過。另以主機環境執行scripts/container_check.py,確認 v0.5.0、加密及 schema v10;實際 amd64/arm64 映像由 PR CI 建置驗證。測試使用模擬 Telegram/供應商及暫存 SQLite,涵蓋雙方同意、按鈕選 Key、權限失敗、群組與個人隔離、撤銷/刪 Key、冷卻/降級及確認流程。未進行真實 Telegram 點擊、真實 Key/付費呼叫或部署驗收。