-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: support --publish
and --canary
#123
Conversation
283b3ee
to
3164854
Compare
--edge
and --publish
Codecov Report
@@ Coverage Diff @@
## main #123 +/- ##
==========================================
- Coverage 71.55% 68.63% -2.92%
==========================================
Files 7 9 +2
Lines 798 880 +82
Branches 81 81
==========================================
+ Hits 571 604 +33
- Misses 227 276 +49
|
Thanks π I have quickly iterated to make some refactors, mainly to introduce this feature as (more generic) name/version suffix options to internal utils. Also introducing feature (CLI shortcut) as (more known) |
--edge
and --publish
--canary
and --publish
--canary
and --publish
--publish
and --canary
Looks great! β€οΈ |
π Linked issue
resolves #105
β Type of change
π Description
This adds support for
--edge
and--publish
flags when passed on CI to do something like:It will automatically enable provenance if running in GitHub Actions, and will bump package version appropriately.
Feedback (and direct edits!) welcome.
π Checklist