Skip to content

Add approval gate for canary publishes #3

@bntvllnt

Description

@bntvllnt

Problem

Canary versions auto-publish to npm on every config change without human review. A broken config goes to the public registry immediately.

Risk

Consumers using @vllnt/typescript@canary get broken configs until next fix.

Options

  1. Add environment: canary with required reviewers in workflow
  2. Change canary to --dry-run + upload artifact for manual verification
  3. Add smoke test gate before canary publish (blocks on failure)

Acceptance Criteria

  • Choose and implement gating strategy
  • Broken configs cannot reach npm without explicit approval or passing tests

Priority

Medium — affects downstream consumers.

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions