-
Notifications
You must be signed in to change notification settings - Fork 85
feat(extension): support multi-extension GitHub release repos #593
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
jkirsteins
wants to merge
13
commits into
DataDog:main
Choose a base branch
from
jkirsteins:janis.kirsteins/multi-extension-repo
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
c9c2155
feat(extension): support shared release repositories
jkirsteins eed1fc4
fix(extension): clarify exact release tag installs
jkirsteins daac203
fix(extension): harden shared release installs
jkirsteins 5ec36c8
fix(extension): make shared archive installs safer
jkirsteins 1df678d
fix(extension): align remote listing with stable installs
jkirsteins 9f9f5e1
fix(extension): bound remote extension archive scans
jkirsteins 65de05a
fix(extension): cap decoded tar archive scans
jkirsteins d4efeb5
fix(extension): cap decoded tar reader
jkirsteins 366b354
fix(extension): harden GitHub auth and rollback
jkirsteins ea0b8ec
fix(extension): unify staged extension writes
jkirsteins a8d0514
docs(wasm): document native-only extensions
jkirsteins b2aa789
Merge remote-tracking branch 'origin/main' into janis.kirsteins/multi…
jkirsteins 8fc8f33
fix(ci): update test configs for jq field
jkirsteins File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The WASI CI/release job builds the CLI with
cargo build --target wasm32-wasip2 --no-default-features --features wasi(.github/workflows/ci.yml:207), but these new archive crates are only enabled by thenativefeature whilesrc/extensions/install.rsnow referencesflate2,tar, andzipunconditionally. That leaves the WASI build without those optional dependencies and the binary will fail to compile; add them to thewasifeature or cfg-gate the archive install code out of that target.Useful? React with 👍 / 👎.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Verified the WASI build locally with:
cargo check --target wasm32-wasip2 --no-default-features --features wasiIt passes because extensions are cfg-gated and not compiled for the WASI target.
Added a line in README.md under WASM limitations.