-
Notifications
You must be signed in to change notification settings - Fork 0
Open
Labels
enhancementNew feature or requestNew feature or request
Description
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
- Add
environment: canarywith required reviewers in workflow - Change canary to
--dry-run+ upload artifact for manual verification - 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.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
enhancementNew feature or requestNew feature or request