Skip to content

Default create-release to blocking unlisted egress and retire its opt-in flag #914

Description

@devantler

🤖 Generated by the Agentic Engineer

Evidence

#912 adds block-egress to create-release.yaml as a default-off release flag. The feature-flag-first rule in the workflow guide says a release flag is short-lived, and its removal is filed when the flag is born. This is that issue.

Audience / problem

Every repository that releases through this workflow. While the flag exists, only callers that remember to set it get the protection, and the flag is one more input to maintain.

Hypothesis

Once one consumer release succeeds in block mode and the refusal control is observed (#912's remaining acceptance), defaulting to block mode protects every caller without breaking any release.

Success signal

After the default flips, release runs across the consumers keep succeeding, and their StepSecurity insights show block mode with no refused host during an ordinary release.

Smallest useful change

  1. Flip block-egress to default true, and watch a window of ordinary consumer releases.
  2. Remove the input, so both release jobs always run in block mode with their allow-list, and update the README and workflow guide to match.

Acceptance criteria

Rough size: S.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Fields

    No fields configured for Security.

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions