You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 47a647c
Browse filesBrowse the repository at this point in the historyBrowse files
Nothing has ever made an artifact readable by the world: CannedACL appears nowhere in this repository's history, so every S3 deployment has depended on a bucket policy to grant it and silently served unreachable firmware where there was none. PublishedArtifactVerifier is what surfaced it, refusing a publish whose every artifact answered 403.
The caller now states whether an object is world-readable, because it is the only thing that knows: staged bytes stay private, the published copy and a module zip do not. The parameter has no default, since a forgotten argument is a release nobody can download and nothing fails until a hub tries.
Sending the ACL is opt-in via Storage:S3:PublicReadAcl. R2 does not implement ACLs and an AWS bucket on the default Object Ownership rejects them, and on both the write fails rather than being ignored, so a bucket granting public read by policy must keep sending none.
0 commit comments