Skip to content

fix: add release-assets.githubusercontent.com to net allowlist#13

Merged
kevinkod merged 1 commit intomainfrom
fix/self-update-net-allowlist
May 1, 2026
Merged

fix: add release-assets.githubusercontent.com to net allowlist#13
kevinkod merged 1 commit intomainfrom
fix/self-update-net-allowlist

Conversation

@kevinkod
Copy link
Copy Markdown
Contributor

@kevinkod kevinkod commented May 1, 2026

Summary

  • specflow self-update was prompting the end user for net access on every release because Deno's compile-time --allow-net allowlist in scripts/build.ts was missing release-assets.githubusercontent.com — the host github.com 302-redirects release-asset downloads to.
  • Adds the missing host to the allowlist. Keeps objects.githubusercontent.com and codeload.github.com as belt-and-braces for any historical or future redirect path.
  • One-time UX caveat: users on v0.6.1 → 0.7.1 still see the prompt once when they self-update to the fixed version (their old binary's permissions are immutable). After they're on the fixed version, future self-updates run silently.

Closes #12.

Test plan

  • Redirect chain confirmed via curl -I -Lgithub.com/mkrlabs/specflow/releases/download/... 302s to release-assets.githubusercontent.com/... then 200s.
  • deno task test — 318 tests pass.
  • Pre-commit hook (fmt + lint + bundle + check) green.
  • Post-merge: release v0.7.2 and run specflow self-update --check from a v0.7.1 binary → expect the prompt once (one-time migration), then on a v0.7.2 binary → expect silent operation.

🤖 Generated with Claude Code

specflow self-update was prompting the end user for net access on every release because Deno's compile-time --allow-net allowlist scopes which hostnames the binary may reach, and release-assets.githubusercontent.com (the actual download host after github.com 302-redirects) was missing.

A compiled binary should never prompt — that defeats one-shot self-update and breaks any non-interactive context (CI, scripted upgrade, fresh install). Adding the redirect target to the allowlist closes the gap.

Note: users on v0.6.1 → 0.7.1 still see the prompt once when they self-update to the fixed version (their old binary's permissions are immutable). After they're on the fixed version, future self-updates run silently.

Closes #12.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@kevinkod kevinkod merged commit 26c62e4 into main May 1, 2026
4 checks passed
@kevinkod kevinkod deleted the fix/self-update-net-allowlist branch May 1, 2026 22:15
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.

fix: add release-assets.githubusercontent.com to compiled binary net allowlist

1 participant