Closed greenkeeper[bot] closed 5 years ago
dependency
@lerna/project was updated from 3.7.2
to 3.10.0
.Update to this version instead 🚀
--include-merged-tags
present (fb2a1b2), closes #1820The new version differs by 18 commits.
ea8ffa7
chore(release): v3.10.0
02a067f
feat(lerna): Use --exact version ranges between sibling dependencies
be7ceaa
chore(config): Move durable command.publish config to proper command.version namespace
fb2a1b2
fix(publish): Correctly determine canary version when --include-merged-tags
present
d73d823
feat(version): Add --no-changelog
option (#1854)
a4f1a92
docs(readme): add config option to lerna.json (#1856) [ci skip]
c2b606c
chore(release): publish v3.9.1
ea9dbbe
fix(bootstrap): Prevent recursive execution from all install lifecycles
e602838
fix(bootstrap): Don't pass --ignore-scripts
to npm install
1c1ac15
chore(release): publish v3.9.0
094a1cb
fix(describe-ref): Properly handle sha-like tag names (#1853)
f14fc06
feat(bootstrap): Add --ignore-prepublish
option
944e36f
feat(bootstrap): Run root install lifecycles where appropriate
929ae22
fix(bootstrap): Only run install lifecycles once-per-package, in topological order
bab8e58
fix(run-lifecycle): Ensure all npm_package_* env vars are created
There are 18 commits in total.
See the full diff
The dependency @lerna/project was updated from
3.7.2
to3.8.5
.This version is not covered by your current version range.
If you don’t accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.
Release Notes for v3.8.5
Bug Fixes
pkg.publishConfig
is handled correctly (1877def), closes #1498--npm-tag
, replaced by--dist-tag
(196d663)pkg.publishConfig
is handled correctly when promoting dist-tags (af1c2ad)Commits
The new version differs by 44 commits.
9f5c824
chore(release): publish v3.8.5
63a7a89
fix(npm-dist-tag): Improve robustness
6c0d1d8
docs(publish): Add 'Per-Package Configuration' section
af1c2ad
fix(publish): Ensure pkg.publishConfig is handled correctly when promoting dist-tags
1877def
fix(npm-publish): Ensure pkg.publishConfig is handled correctly
5a04145
fix(publish): Tweak progress logging
c528758
refactor(npm-publish): Only accept tag via options
196d663
fix(publish): Deprecate
--npm-tag
, replaced by--dist-tag
7a65a87
fix(project): Deprecate root-level config keys as well, prioritizing nested
5075d8c
docs(publish): Clarify options, shuffle order, fix indent
c7fa580
chore(release): publish v3.8.4
31982a1
fix(publish): Pass username to access.lsPackages()
4300a07
chore(release): publish v3.8.3
b44f2f9
fix(publish): Give up trying to validate third-party registries
25da088
chore(release): publish v3.8.2
There are 44 commits in total.
See the full diff
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper bot :palm_tree: