Skip to content

Pin app-store to v1.0.1 release tag#321

Merged
TeoSlayer merged 1 commit into
mainfrom
bump-app-store-v1.0.1
Jun 23, 2026
Merged

Pin app-store to v1.0.1 release tag#321
TeoSlayer merged 1 commit into
mainfrom
bump-app-store-v1.0.1

Conversation

@TeoSlayer

Copy link
Copy Markdown
Collaborator

Replaces the pseudo-version v1.0.1-beta.1.0.20260623120425-df0e4a35d764 introduced in #317 with the clean v1.0.1 release tag that app-store just published.

Why

app-store cut a real v1.0.1 tag at the exact commit web4 already pins (df0e4a35). This swaps the messy pseudo-version for the proper semver tag so the next pilotctl release ships against a real version string.

What's included in v1.0.1

Both were already built against via the pseudo-version, so this is a version-string-only change — no code differences.

Verification

  • Tag v1.0.1 resolves to commit df0e4a35d7642bc395f4e3e53e2d65e124c57eaf — identical to the pseudo-version's df0e4a35d764.
  • Extracted module source trees for the two versions are byte-identical (diff -r clean); the /go.mod hash in go.sum is unchanged.
  • GOWORK=off go build ./... — clean
  • GOWORK=off go vet ./... — clean
  • GOWORK=off go test ./cmd/pilotctl/... — pass, including TestProcExecCapabilityAccepted
  • gofmt — clean
  • govulncheck ./... — No vulnerabilities found

Diff is limited to go.mod / go.sum.

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.
@TeoSlayer TeoSlayer merged commit f137d88 into main Jun 23, 2026
12 of 13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants