fix(share): refuse an unreadable .hyperframesignore when a snapshot picks files to send (#7573)

0.9.35 made snapshotProject and snapshotFiles fall back to scratch-only
exclusions when .hyperframesignore can't be read. That is right for change
detection, but a host that builds an archive from the same snapshot then
includes files the ignore file meant to exclude, including ones named on its
valid lines.

The snapshot is strict again by default and throws invalid_source_ignore.
Change detection opts in with { lenientIgnore: true }, and projectFingerprint,
which names no files, always reads leniently.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
terencecho
2026-11-12 00:47:42 +00:00
committed by GitHub
co-authored by Claude Opus 5.5
parent f66c673d19
commit 35cf03cab9
4 changed files with 52 additions and 18 deletions
+4 -3
View File
@@ -56,9 +56,10 @@ These rules can only exclude files, never re-include credentials or other files
blocked by the portable project policy.
Cloud render reads the same file as gitignore syntax, so it may hold rules this
reader rejects, such as `/exports/` or `**/*.mov`. Source capture then stops with
an error. Change detection keeps working and ignores the file's rules, so those
files still count as changes.
reader rejects, such as `/exports/` or `**/*.mov`. Source capture, and anything
else that picks project files to upload, then stops with an error. Change
detection keeps working and ignores the file's rules, so those files still count
as changes.
The upload uses the workspace's file-count, per-file, project-size and manifest
limits. Large media uploads in parts. Only a verified published snapshot that