canary automation releases un-published packages
Open
- Dominant language
- TypeScript
- Stars
- 16.9k
- Forks
- 1.9k
- Avg merge
- 22h 45m
- Merged PRs (30d)
- 70
Description
this could be a subject for debate - should the canary pipeline automatically publish canary releases of new (unreleased) packages?
or should it do a quick check via an HTTP request to npm to see if it 404s, and skip if so?
Contributor guide
Assessment
This issue has not been assessed yet.