Fix workspace shared file approval visibility and harden distroless runtime overlay packaging in Dockerfile - #1414
Merged
Paul Lizer (paullizer) merged 4 commits intoSep 4, 2026
Conversation
…appear for approval.
…e copy, updated assoicated test files.
Paul Lizer (paullizer)
merged commit Sep 4, 2026
d5ef183
into
microsoft:Development
11 of 12 checks passed
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.
Summary
This PR fixes two production-impacting issues:
Release Notes & Latest Features
Is this visible to end users?
Is this admin-facing (Admin Settings, governance, deployment, config)?
Should this become a Latest Feature card?
Screenshot needed for the card?
Version bump
application/single_app/config.pyVERSIONthird segment bumped, or not needed because this is docs-onlydeployers/version.txtbumped, or not needed becausedeployers/was not changedProblem Details
1) Shared approval visibility regression
Pending approval files are intentionally not automatically granted. The scope projection query filtered on granted access only, which hid eligible pending files from approvers.
2) Distroless overlay path conflict
The builder staged runtime trees that could materialize usr/lib64 as a directory, then copied those trees into a distroless base where /usr/lib64 may be a non-directory entry (for example symlink). BuildKit rejects that overlay.
Build error 1:
Build error 2:
What Changed
Access index fix
Changed file:
Dockerfile/runtime packaging fix
Changed files:
Test alignment and docs
Changed files:
Validation
File sharing bug
File now appears in target workspace with Approve button

Confirmation pop-up appears

And then file is available in target workspace

Dockerfile bug
This command now runs without errors
Passed
Known failing check
Documentation
Security checklist
@swagger_route(security=get_auth_security())sanitize_settings_for_user()