Skip to content

feat(auth): request Basilisk query scope - #2655

Open
tdejager wants to merge 1 commit into
mainfrom
pfx-1798-basilisk-query-scope
Open

feat(auth): request Basilisk query scope#2655
tdejager wants to merge 1 commit into
mainfrom
pfx-1798-basilisk-query-scope

Conversation

@tdejager

@tdejager tdejager commented Aug 7, 2026

Copy link
Copy Markdown
Collaborator

Description

pixi audit will use prefix.dev access tokens to query Basilisk. Rattler's built-in prefix.dev client currently asks for identity and channel scopes only, so those tokens cannot call the authenticated query API.

This adds basilisk:query to the shared prefix.dev OAuth defaults used by the authorization-code and device-code flows without dropping the existing channel scopes. Refresh requests continue to omit scope, which preserves the original grant. Users with an existing login will need to upgrade to a Pixi release containing this change, then log out and back in.

PFX-1798

How Has This Been Tested?

  • Formatting and workspace Clippy pass.
  • Focused auth tests cover the complete prefix.dev default scope set.
  • Refresh tests assert that refresh requests do not replace the original grant.

AI Disclosure

  • This PR contains AI-generated content.
    • I have tested any AI-generated content in my PR.
    • I take responsibility for any AI-generated content in my PR.

Tools: OpenAI Codex via pi

Add basilisk:query to prefix.dev's shared OAuth defaults, preserve the existing channel grant during refresh, cover the auth flows, add re-login guidance, and validate the change.

Checklist

  • I have performed a self-review of my own code
  • I have commented the refresh behavior where it is easy to regress
  • I have made corresponding changes to the documentation
  • I have added sufficient tests to cover my changes

@baszalmstra
baszalmstra enabled auto-merge (squash) August 7, 2026 15:34
@baszalmstra
baszalmstra disabled auto-merge August 7, 2026 15:34

### Changed

- prefix.dev OAuth logins now request Basilisk query access while retaining channel access. Pixi users must upgrade to the eventual Pixi release containing this change, then run `pixi auth logout prefix.dev` and `pixi auth login prefix.dev` to update existing credentials.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this can be removed its auto generated

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants