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
Support --use-version argument with shipit #2075
Conversation
Codecov Report
@@ Coverage Diff @@
## main #2075 +/- ##
==========================================
- Coverage 80.24% 80.19% -0.06%
==========================================
Files 66 66
Lines 5397 5403 +6
Branches 1251 1254 +3
==========================================
+ Hits 4331 4333 +2
- Misses 706 709 +3
- Partials 360 361 +1
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looking good. just a few things I need addressed
@hipstersmoothie I have addressed your PR comments, let me know if you need anything else! |
🚀 PR was released in |
What Changed
Updated the
auto shipit
command to enable setting the--use-version
flag. (Currently only supported for the npm plugin)Additional Changes:
.editorconfig
to force consistency across dev environmentsgetLatestReleasedTagWithPattern
to provide better support for GitHub "release" version based on a provided pattern.Why
There are use cases where we want to specify the version to release through
shipit
. In particular, when maintaining multiple old version branches, version calculations are computed incorrectly. In order to support complex semantic release workflows through npm, this is a temporary solution until the root cause can be determined (i.e.oldRelease()
) .Todo:
Change Type
Indicate the type of change your pull request is:
documentation
patch
minor
major