-
Notifications
You must be signed in to change notification settings - Fork 205
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
fix(npm): mark releases as latest with lerna #2414
fix(npm): mark releases as latest with lerna #2414
Conversation
@intuit any chance to get it merged? Having same problem causing incorrect change logs and version numbers |
281b903
to
50e3b29
Compare
Co-authored-by: Jack Westbrook <jack.westbrook@gmail.com>
50e3b29
to
a55aac0
Compare
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.
Beauuuuuutiful
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #2414 +/- ##
==========================================
- Coverage 80.65% 80.57% -0.09%
==========================================
Files 69 69
Lines 5676 5677 +1
Branches 1274 1275 +1
==========================================
- Hits 4578 4574 -4
- Misses 718 719 +1
- Partials 380 384 +4 ☔ View full report in Codecov by Sentry. |
Looks like it's passing the CI checks! (other than the two that seem to have some other issues) Anything preventing from releasing this? |
🚀 PR was released in |
What Changed
Mark the releases as "latest" when releasing with the npm plugin with the independent mode.
Why
Currently
auto
gets the latest release by looking for a release that is marked as "latest". Thenpm
plugin does not update the "latest" tag when releasing with independent mode causing the releases to start diffing from the initial release.Todo:
Change Type
Indicate the type of change your pull request is:
documentation
patch
minor
major