This repository has been archived by the owner on Feb 18, 2024. It is now read-only.

Refresh lockfile & bump in-range dependency versions #1356

Merged

edmorley merged 1 commit into neutrinojs:master from edmorley:bump-in-range-deps

Apr 14, 2019

Member

edmorley commented Apr 14, 2019

Bumping the versions in theory shouldn't be necessary, however package managers tend to only update sub-dependencies lazily, so this ensures users are on the latest versions.


          Refresh lockfile & bump in-range dependency versions

f5a0f77

Bumping the versions in theory shouldn't be necessary, however package
managers tend to only update sub-dependencies lazily, so this ensures
users are on the latest versions.

edmorley added the cleanup label

edmorley added this to the Neutrino 9 milestone

edmorley self-assigned this

Member Author

edmorley commented Apr 14, 2019 •

edited

Loading

These changes were generated using npm-check-updates v3, by:

yarn global add npm-check-updates
Check to see if any packages need excluding (eg deepmerge), using yarn && yarn outdated
From the root of the repo, run eg (remove the -u to dry run):
- ncu -x deepmerge,ava -u
- for d in packages/*; do ncu --dep prod,dev -x deepmerge,ava --packageFile "${d}/package.json" -u; echo; done
Regenerate the lockfile using rm -rf yarn.lock && yarn

edmorley merged commit f046ef6 into neutrinojs:master

edmorley deleted the bump-in-range-deps branch

April 14, 2019 15:03

edmorley mentioned this pull request

Bump in-range dependency versions #1445

Merged

edmorley added a commit that referenced this pull request


          Bump in-range dependency versions (#1445)

108b173

Bumping the versions in theory shouldn't be necessary, however package
managers tend to only update sub-dependencies lazily, so this ensures
users are on the latest versions.

Changes made using the approach described here:
#1356 (comment)

edmorley added a commit that referenced this pull request


          Bump in-range dependency versions

3a5747e

Bumping the versions in theory shouldn't be necessary, however package
managers tend to only update sub-dependencies lazily, so this ensures
users are on the latest versions.

Changes made using the approach described here:
#1356 (comment)

edmorley pushed a commit that referenced this pull request


          Lock file maintenance (#1483)

af84046

And also:
* Run `yarn prettier:fix`
* Bump in-range dependency versions

Bumping the versions in theory shouldn't be necessary, however package
managers tend to only update sub-dependencies lazily, so this ensures
users are on the latest versions.

Changes made using the approach described here:
#1356 (comment)

edmorley added a commit that referenced this pull request


          Bump in-range dependency versions

751a412

Bumping the versions in theory shouldn't be necessary, however package
managers tend to only update sub-dependencies lazily, so this ensures
users are on the latest versions.

Changes made using the approach described here:
#1356 (comment)

edmorley pushed a commit that referenced this pull request


          Lock file maintenance (#1490)

2d8672b

And:
* Update copy plugin test to pass valid options
   Since `copy-webpack-plugin` now validates the patterns passed, as of:
   webpack-contrib/copy-webpack-plugin/pull/419
* Bump in-range dependency versions
   Bumping the versions in theory shouldn't be necessary, however package
   managers tend to only update sub-dependencies lazily, so this ensures
   users are on the latest versions.

   Changes made using the approach described here:
   #1356 (comment)

edmorley added a commit that referenced this pull request


          Bump in-range dependency versions

6f01c88

Bumping the versions in theory shouldn't be necessary, however package
managers tend to only update sub-dependencies lazily, so this ensures
users are on the latest versions.

Changes made using the approach described here:
#1356 (comment)

edmorley added a commit that referenced this pull request


          Lock file maintenance (#1509)

5e9c89e

And bump in-range dependency versions.

Bumping the versions in theory shouldn't be necessary, however package
managers tend to only update sub-dependencies lazily, so this ensures
users are on the latest versions.

Changes made using the approach described here:
#1356 (comment)

Co-authored-by: Ed Morley <501702+edmorley@users.noreply.github.com>

edmorley added a commit that referenced this pull request


          Bump in-range dependency versions.

7ec8875

Bumping the versions in theory shouldn't be necessary, however package
managers tend to only update sub-dependencies lazily, so this ensures
users are on the latest versions.

Changes made using the approach described here:
#1356 (comment)

edmorley added a commit that referenced this pull request


          Lock file maintenance (#1545)

8ca32d9

And bump in-range dependency versions.

Bumping the versions in theory shouldn't be necessary, however package
managers tend to only update sub-dependencies lazily, so this ensures
users are on the latest versions.

Changes made using the approach described here:
#1356 (comment)

Co-authored-by: Ed Morley <501702+edmorley@users.noreply.github.com>

edmorley added a commit that referenced this pull request


          Bump in-range dependency versions

f0c893d

Bumping the versions in theory shouldn't be necessary, however package
managers tend to only update sub-dependencies lazily, so this ensures
users are on the latest versions.

Changes made using the approach described here:
#1356 (comment)

edmorley added a commit that referenced this pull request


          Lock file maintenance (#1558)

faf5ff2

And bump in-range dependency versions...

Bumping the versions in theory shouldn't be necessary, however package
managers tend to only update sub-dependencies lazily, so this ensures
users are on the latest versions.

Changes made using the approach described here:
#1356 (comment)

Co-authored-by: Ed Morley <501702+edmorley@users.noreply.github.com>

edmorley added a commit that referenced this pull request


          Bump in-range dependency versions...

3fec67d

Bumping the versions in theory shouldn't be necessary, however package
managers tend to only update sub-dependencies lazily, so this ensures
users are on the latest versions.

Changes made using the approach described here:
#1356 (comment)

edmorley added a commit that referenced this pull request


          Lock file maintenance (#1573)

fa3669d

And bump in-range dependency versions...

Bumping the versions in theory shouldn't be necessary, however package
managers tend to only update sub-dependencies lazily, so this ensures
users are on the latest versions.

Changes made using the approach described here:
#1356 (comment)

Co-authored-by: Ed Morley <501702+edmorley@users.noreply.github.com>

edmorley added a commit that referenced this pull request


          And bump in-range dependency versions...

601542c

Bumping the versions in theory shouldn't be necessary, however package
managers tend to only update sub-dependencies lazily, so this ensures
users are on the latest versions.

Changes made using the approach described here:
#1356 (comment)

edmorley added a commit that referenced this pull request


          Lock file maintenance (#1583)

cf1967a

And bump in-range dependency versions...

Bumping the versions in theory shouldn't be necessary, however package
managers tend to only update sub-dependencies lazily, so this ensures
users are on the latest versions.

Changes made using the approach described here:
#1356 (comment)

Co-authored-by: Ed Morley <501702+edmorley@users.noreply.github.com>

edmorley added a commit that referenced this pull request


          Bump in-range dependency versions

a1826ce

Bumping the versions in theory shouldn't be necessary, however package
managers tend to only update sub-dependencies lazily, so this ensures
users are on the latest versions.

Changes made using the approach described here:
#1356 (comment)

edmorley added a commit that referenced this pull request


          Lock file maintenance (#1599)

5eb98b9

And bump in-range dependency versions...

Bumping the versions in theory shouldn't be necessary, however package
managers tend to only update sub-dependencies lazily, so this ensures
users are on the latest versions.

Changes made using the approach described here:
#1356 (comment)

Co-authored-by: Ed Morley <501702+edmorley@users.noreply.github.com>

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels