Add content-type input to override auto-detection#11
Merged
Conversation
jason-rl
force-pushed
the
feat/content-type-override
branch
from
3d8ea65 to
543b9bc
Compare
- Add `content-type` input to override auto-detected content type - Include `unspecified` as a valid value (matches backend/frontend) - Rewrite `determineContentType` to verify file contents against extensions using magic bytes: gzip header (1f 8b), tar header (ustar at offset 257), and decompressed tar-inside-gzip check - Warn when extension doesn't match actual file contents - Fall back to content-based heuristics when no extension matches Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
jason-rl
force-pushed
the
feat/content-type-override
branch
from
543b9bc to
7b4c08e
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.
Summary
content-typeinput toaction.ymlacceptingtext,binary,gzip,tar, ortgzContext
.tgzfiles uploaded viasource-type: filewere auto-detected astgz, causing rage to extract them as archives. Public npm agents needcontent-type: binaryso the tarball is placed as a single file fornpm install -g ./file.tgz.Test plan
content-type: binaryand a.tgzfilecontent-typeand verify auto-detection still works🤖 Generated with Claude Code