go.mod: bump app-store to the proc.exec version#317
Merged
Conversation
Repoint the pinned app-store dependency to the commit that adds the proc.exec capability, so the daemon's manifest validation accepts CLI apps (which ship a proc.exec grant scoped to one command). Without the bump, the deployed daemon validates against a capability vocabulary that lacks proc.exec and rejects them. No daemon code changes: pilotctl/supervisor already delegate validation to app-store's manifest.Validate(). Adds a regression test asserting a proc.exec manifest validates (and that a wildcard target is still rejected). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Collaborator
|
The only red check is "Go (macos-latest)", which was the macOS runner |
Resolve go.mod/go.sum conflict by keeping all of main's current dependency versions and bumping github.com/pilot-protocol/app-store to v1.0.1-beta.1.0.20260623120425-df0e4a35d764, the latest published commit. This version is a descendant of app-store #23 (trust-anchor enforcement) and #24 (proc.exec capability), so it carries both the security fix and the proc.exec feature. Keep the PR's proc.exec regression test.
TeoSlayer
added a commit
that referenced
this pull request
Jun 23, 2026
Replace the pseudo-version v1.0.1-beta.1.0.20260623120425-df0e4a35d764 from #317 with the clean v1.0.1 release tag. The tag points at the exact same commit (df0e4a35), so this is a version-string-only change with no code differences. Includes proc.exec capability and the trust-anchor fix already built against by web4. Co-authored-by: Teodor Calin <teodor@vulturelabs.io>
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
3 participants
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.
Repoints the pinned
github.com/pilot-protocol/app-storedependency to the commit that adds theproc.execcapability, so the daemon's manifest validation accepts CLI apps (which ship aproc.execgrant scoped to one command). Without the bump, the deployed daemon validates against a capability vocabulary that lacksproc.execand rejects them.Depends on pilot-protocol/app-store#24; re-pin to the merged SHA once it lands.
Footprint: zero business logic
This is deliberately a dependency-pointer + test change only. The
proc.execlogic lives entirely in the app-store dependency —pilotctl/supervisor already delegate validation toapp-store'smanifest.Validate(), so nothing in this repo duplicates or implements capability logic. Diff isgo.mod+go.sum+ one test.Test
cmd/pilotctlregression test asserting aproc.execmanifest validates against the pinned app-store (and that a wildcard*target is still rejected by the hardened validator).🤖 Generated with Claude Code