syntaqxA workspace token for all of its workspace's repositories is held to that workspace. Identity resolved such a token with no reach (only a token for chosen repositories had one), so the API's resource-owner check never applied to it: with issues or pull-requests write it could open issues, comment or open pull requests on any other workspace's public repository as the workspace, which the docs said it could not. apply_reach now gives every workspace token a reach of its own workspace, all of its repositories or the ones chosen (workspace_token_reach), the shape a person's token made for one workspace already has; outside it, it reads public repositories as anyone may and changes nothing (token:resource-owner). Inside its workspace nothing changes. Checked: cargo test -p g1t-identity --lib (177, new: a workspace token never writes outside its workspace, for all or chosen repositories; one for all covers its own repositories only) and its wasm32 check.b235b5eHistory
- ..
- backup.test.ts
- backup.ts
- broker-egress.ts
- broker-relay.test.ts
- broker-relay.ts
- broker.test.ts
- broker.ts
- bump.test.ts
- bump.ts
- credentials.test.ts
- credentials.ts
- egress.test.ts
- egress.ts
- forward.test.ts
- forward.ts
- gate.test.ts
- guard.ts
- index.ts
- lifecycle.test.ts
- lifecycle.ts
- machines.test.ts
- self-hosted.test.ts
- self-hosted.ts