fix(files): enforce record and field authorization - #136
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
File operations now enforce the same record policy and field permissions used by entity access before issuing storage access or running mutation hooks. Upload and confirmation require update permission. The shared tenant middleware continues to supply the selected program context, including accounts with multiple memberships.
Eight route regressions cover tenant and owner boundaries, selected/missing/unauthorized program context, field read/write restrictions, authenticated access and administrator behavior. Package patch versions advance the acton crate to 0.36.1 and CLI to 0.37.3. A separate small commit fixes an existing loop lint exposed by Rust 1.97 without suppression.
Validation:
No production deployment is included in this PR.