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
feat: add extra_files manifest field (bundle prebuilt files/binaries into the package)
A [[lambda.extra_files]] entry stages a prebuilt file or directory (src,
repo-root-relative; dest, package-root-relative; optional +x) into the package
source tree, so it ships in the zip and folds into the content hash. The
executable bit folds into the hash separately. Lets a lambda vendor CI-built
binaries / release trees while the tool stays free of download logic. Specs
with no extra_files hash byte-identically to before.
Copy file name to clipboardExpand all lines: CHANGELOG.md
+5Lines changed: 5 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,10 @@
1
1
# Changelog
2
2
3
+
## v0.4.0 - 2026-06-21
4
+
5
+
### Added
6
+
-`extra_files` manifest field: bundle prebuilt files or directories into a lambda package alongside its source. Each `[[lambda.extra_files]]` entry has `src` (repo-root-relative, where CI materialized it - e.g. a digest-pinned binary or an extracted release tree), `dest` (package-root-relative), and an optional `executable` flag (sets +x on a file; ignored for directories, which keep source perms). The bytes fold into the content hash via the staged source tree, and the executable bit folds in separately, so flipping it changes the artifact hash even when bytes are identical. This lets a lambda ship vendored CLIs or release trees the consumer's CI downloads and verifies, while the tool itself stays free of any network/tool-download logic. Paths are validated as relative and `..`-free. Specs without `extra_files` hash byte-identically to before.
0 commit comments