POC: discover extensions bundled with the release archive - #882
Draft
tedkahwaji wants to merge 1 commit into
Draft
tedkahwaji wants to merge 1 commit into
tedkahwaji wants to merge 1 commit into
Conversation
Lets a pup release ship first-party extensions so they work right after installing pup, with no `pup extension install` step. - Look up extensions in libexec/pup-extensions/ next to the binary or one level up (Homebrew layout); user-installed extensions still win - Bundled lookup only accepts valid extension names and regular files - Linux release config fetches a pinned pup-setup asset, verifies its SHA-256, and places it in the archive (placeholder pin and sums) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This branch has not been deployed
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.
POC, not intended to be merged. This stays in draft to explore shipping an extension with every pup release.
Design doc (Datadog internal): Consolidating the AI Setup CLI with Pup
What it does
pup finds extensions shipped in
libexec/pup-extensions/next to its binary (both the tarball and Homebrew layouts), and a user-installed extension still takes precedence. The Linux release config downloads a pinned, checksum-verified extension into the archive. The pin is a placeholder.Testing
🤖 Generated with Claude Code