feat(auth): MiAuth permissions を chat scope に置換#13
Merged
Conversation
Misskey v2025 (#15686) の `chat/*` エンドポイントは新スコープ `read:chat` / `write:chat` を要求する (例: chat/messages/create-to-user → write:chat, chat/history → read:chat)。 旧 `read:messaging` / `write:messaging` は legacy `messaging/*` 用で、 v2025 で対象 API が完全削除されたため新スコープに置換する。NoteDeck は β リリース段階で既存トークンの後方互換性を保つ必要は無い。
hitalin
force-pushed
the
feat/oauth-add-chat-scopes
branch
from
b835fef to
6694826
Compare
hitalin
changed the title
2 tasks
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
1 participant
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.
Summary
Misskey v2025 (#15686) の
chat/*エンドポイントは新スコープread:chat/write:chatを要求する (misskey-js/src/consts.tsのpermissions[]参照)。例:chat/messages/create-to-user→kind: 'write:chat'chat/history→kind: 'read:chat'旧
read:messaging/write:messagingは legacymessaging/*用で、v2025 で対象 API が完全削除されたため、後方互換を残す意味が無い (NoteDeck はβリリース段階)。新スコープに 置換 する。Why
新 NoteDeck で初回認証したユーザーは現状 v2025+ サーバーで chat 操作 (送信・削除・履歴取得) が
AUTHENTICATION_FAILEDになる可能性がある。本 PR で再認証フローから新スコープを取得することでこのリスクを除去する。Test plan
cargo build --features specta通過cargo test --features specta通過read:chat/write:chatが含まれることを確認