Skip to content

v0.6.1

  • v0.6.1
  • 899b9f2

  • Verified

    This commit was created on GitHub.com and signed with GitHub’s verified signature.
    GPG key ID: B5690EEEBB952194
    Verified
    Learn about vigilant mode

  • Choose a tag to compare

    View all tags
v0.6.1: Release 0.6.1: a team access token names its team (#19)
  • v0.6.1
  • 899b9f2

  • Choose a tag to compare

    View all tags

  • Verified

    This commit was created on GitHub.com and signed with GitHub’s verified signature.
    GPG key ID: B5690EEEBB952194
    Verified
    Learn about vigilant mode
@nicu-chiciuc nicu-chiciuc tagged this 21 Oct 15:09 
* Release 0.6.1: a team access token names its team

0.6.0 resolved a team slug through the dashboard's team list, which a team
access token cannot read (HTTP 403 NotAllowed), so every run with
CONVEX_ACCESS_TOKEN from the dashboard failed. resolveTeamId now reads
GET /token_details first, once for each service: a team token names its
team there, and a configured slug is a label. The Convex CLI login gets
403 NotOAuthTeamToken from it and keeps the slug lookup. Convex.state()
takes no team with a team access token.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

* Fold in the review: a configured slug must be the team of the token

A slug that is set with a team access token is checked against the
teamSlug of the team's projects, so a token of another team fails the run
instead of putting resources and state into its own team. A team without a
project cannot be checked and asks for the numeric id, or no team.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

---------

Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
Assets 2
Loading