Sharing a provider key with a whole project is now something you choose
deliberately, and account roles can be changed from a group's member list.
New
- Edit a person's account role from a group's member list. You no longer
have to leave the group to change what someone is.
Improved
- A new API key or ChatGPT account is private by default. The Add dialog
opens with "Specific members" selected and you already on the list, so
sharing a key with everyone in the project is an explicit choice rather than
the default. - One place to pick provider keys for a session, and the choice saves.
Fixed
- Sessions stay usable after the project's repository changes.
- Every role assignment is checked against the owner ceiling, so an assignment
cannot grant more than the person making it holds.
What's Changed
- feat(web): pooled provider secrets default to Specific members + you by @markokraemer in #7458
- Edit a person's account role from a group's member list by @markokraemer in #7459
- fix(web): session provider keys save + one place to pick keys by @markokraemer in #7462
- Enforce the owner ceiling on every IAM assignment write by @markokraemer in #7460
- fix: keep sessions usable after repository changes by @markokraemer in #7463
- chore(release): VERSION → 0.13.27 [skip ci] by @github-actions[bot] in #7465
- chore(release): staging VERSION → 0.13.27 [skip ci] by @github-actions[bot] in #7466
- fix(agent-tunnel): declare the repository so npm provenance validates by @markokraemer in #7467
- test(web): 28-model-access follows the new sharing default by @markokraemer in #7473
- Promote main to staging for v0.13.27 by @markokraemer in #7469
- Release v0.13.27 — Provider keys are private by default, and account roles are editable from a group by @github-actions[bot] in #7475
Full Changelog: v0.13.26...v0.13.27