Add explicit error handling for SAM build artifacts#96
Merged
Conversation
Member
smessmer
commented
Jan 11, 2026
smessmer
commented
- Add verification step to check .aws-sam directory exists after build
- Add if-no-files-found: error to fail explicitly if artifacts are missing
smessmer
force-pushed
the
debug-artifact-upload
branch
3 times, most recently
from
6c1f89b to
2f7003b
Compare
- Use npm run build to ensure esbuild is on PATH - Include hidden files for .aws-sam artifact upload - Error if no artifacts found
smessmer
force-pushed
the
debug-artifact-upload
branch
from
2f7003b to
8fc5a94
Compare
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
1 participant
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.