Skip to content

fix: require update permission to recreate devcontainers (#25812)#26258

Merged
f0ssel merged 2 commits into
release/2.34from
cherry-pick/25812/release/2.34
Jun 11, 2026
Merged

fix: require update permission to recreate devcontainers (#25812)#26258
f0ssel merged 2 commits into
release/2.34from
cherry-pick/25812/release/2.34

Conversation

@jdomeracki-coder

Copy link
Copy Markdown
Contributor

Cherry-pick backport to release/2.34.

- The httpmw upstream from this endpoint only checks for read perms to the
workspace agent. Recreating a dev container should require `update`
perms since it mutates state. This also matches the behavior of the
`DELETE` endpoint

(cherry picked from commit bb11946)
@jdomeracki-coder jdomeracki-coder added the cherry-pick/v2.34 Cherry-pick PR targeting release/2.34 label Jun 11, 2026
@jdomeracki-coder jdomeracki-coder requested review from f0ssel and sreya June 11, 2026 14:40
@f0ssel f0ssel merged commit e822677 into release/2.34 Jun 11, 2026
27 checks passed
@f0ssel f0ssel deleted the cherry-pick/25812/release/2.34 branch June 11, 2026 17:59
@github-actions github-actions Bot locked and limited conversation to collaborators Jun 11, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

cherry-pick/v2.34 Cherry-pick PR targeting release/2.34

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants