Support modern node, amongst other things #14
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
I mean, they're used on the splash screen, but they're still icons no? Per GoogleChrome/lighthouse#291 (comment)
[skip ci] # [2.1.0](v2.0.4...v2.1.0) (2019-03-10) ### Features * Add PWA splash screen icons. ([2ee286c](2ee286c)), closes [/github.com/GoogleChrome/lighthouse/issues/291#issue-153328672](https://github.com//github.com/GoogleChrome/lighthouse/issues/291/issues/issue-153328672) * **travis:** `android-icons` -> `[@randy](https://github.com/randy).tarampi/android-icons` ([52db43a](52db43a))
There's some weirdness with the travis boxes where they don't seem to be able to find cached modules... Per https://travis-ci.com/randytarampi/lwip/jobs/183637295. ``` npm WARN prepare removing existing node_modules/ before installation npm ERR! code MODULE_NOT_FOUND npm ERR! Cannot find module '../pack.js' ```
BREAKING CHANGE: Drop support for node 4 and earlier, since `yargs^13.2.2` requires ES6 support.
[skip ci] # [3.0.0](v2.1.0...v3.0.0) (2019-03-10) ### Bug Fixes * **package:** Since the package updates we no longer support node@4. ([17bea94](17bea94)) * **travis:** Don't bother caching dependencies. ([fcc5cf4](fcc5cf4)) ### BREAKING CHANGES * **package:** Drop support for node 4 and earlier, since `yargs^13.2.2` requires ES6 support.
…support node@10, node@12 and beyond. At least it'll get tested...
[skip ci] # [3.1.0](v3.0.0...v3.1.0) (2020-01-06) ### Features * **package:** Blindly upgrade our dependencies for the new year and support node@10, node@12 and beyond. ([269473e](269473e))
Merge pull request #5 from randytarampi/greenkeeper/semantic-release-16.0.0
The tools work on node@8, it's just the packaging that's to blame here.
The following vulnerabilities are fixed with an upgrade: - https://snyk.io/vuln/SNYK-JS-YARGSPARSER-560381
…7ae801b88441 [Snyk] Security upgrade yargs from 15.1.0 to 15.3.0
[skip ci] ## [3.1.1](v3.1.0...v3.1.1) (2020-04-19) ### Bug Fixes * package.json & package-lock.json to reduce vulnerabilities ([e9a1328](e9a1328))
chore(greenkeeper): Update tape
Goodbye Greenkeeper 👋
Snyk has created this PR to upgrade semantic-release from 17.0.0 to 17.0.7. See this package in NPM: https://www.npmjs.com/package/semantic-release See this project in Snyk: https://app.snyk.io/org/randytarampi/project/e8e28cfe-0638-4e7a-bdc6-c6bc4fe6b526?utm_source=github&utm_medium=upgrade-pr
Snyk has created this PR to upgrade semantic-release from 17.0.0 to 17.0.7. See this package in NPM: https://www.npmjs.com/package/semantic-release See this project in Snyk: https://app.snyk.io/org/randytarampi/project/e8e28cfe-0638-4e7a-bdc6-c6bc4fe6b526?utm_source=github&utm_medium=upgrade-pr
Snyk has created this PR to upgrade standard from 14.3.1 to 14.3.3. See this package in NPM: https://www.npmjs.com/package/standard See this project in Snyk: https://app.snyk.io/org/randytarampi/project/e8e28cfe-0638-4e7a-bdc6-c6bc4fe6b526?utm_source=github&utm_medium=upgrade-pr
Snyk has created this PR to upgrade standard from 14.3.1 to 14.3.3. See this package in NPM: https://www.npmjs.com/package/standard See this project in Snyk: https://app.snyk.io/org/randytarampi/project/e8e28cfe-0638-4e7a-bdc6-c6bc4fe6b526?utm_source=github&utm_medium=upgrade-pr
Snyk has created this PR to upgrade yargs from 15.3.0 to 15.3.1. See this package in NPM: https://www.npmjs.com/package/yargs See this project in Snyk: https://app.snyk.io/org/randytarampi/project/e8e28cfe-0638-4e7a-bdc6-c6bc4fe6b526?utm_source=github&utm_medium=upgrade-pr
Snyk has created this PR to upgrade yargs from 15.3.0 to 15.3.1. See this package in NPM: https://www.npmjs.com/package/yargs See this project in Snyk: https://app.snyk.io/org/randytarampi/project/e8e28cfe-0638-4e7a-bdc6-c6bc4fe6b526?utm_source=github&utm_medium=upgrade-pr
Snyk has created this PR to upgrade @semantic-release/changelog from 5.0.0 to 5.0.1. See this package in NPM: https://www.npmjs.com/package/@semantic-release/changelog See this project in Snyk: https://app.snyk.io/org/randytarampi/project/e8e28cfe-0638-4e7a-bdc6-c6bc4fe6b526?utm_source=github&utm_medium=upgrade-pr
Snyk has created this PR to upgrade @semantic-release/changelog from 5.0.0 to 5.0.1. See this package in NPM: https://www.npmjs.com/package/@semantic-release/changelog See this project in Snyk: https://app.snyk.io/org/randytarampi/project/e8e28cfe-0638-4e7a-bdc6-c6bc4fe6b526?utm_source=github&utm_medium=upgrade-pr
…543564d025cc586fc [Snyk] Upgrade @semantic-release/changelog from 5.0.0 to 5.0.1
…359428ad507051b26 [Snyk] Upgrade yargs from 15.3.0 to 15.3.1
…125d9c7a37034d013 [Snyk] Upgrade standard from 14.3.1 to 14.3.3
…96ba07c6b0761c4c9 [Snyk] Upgrade semantic-release from 17.0.0 to 17.0.7
[skip ci] ## [3.1.2](v3.1.1...v3.1.2) (2020-04-30) ### Bug Fixes * upgrade @semantic-release/changelog from 5.0.0 to 5.0.1 ([6924876](6924876)) * upgrade @semantic-release/changelog from 5.0.0 to 5.0.1 ([f025f0b](f025f0b)) * upgrade semantic-release from 17.0.0 to 17.0.7 ([59fccc1](59fccc1)) * upgrade semantic-release from 17.0.0 to 17.0.7 ([edaea41](edaea41)) * upgrade standard from 14.3.1 to 14.3.3 ([ee84324](ee84324)) * upgrade standard from 14.3.1 to 14.3.3 ([b6318f8](b6318f8)) * upgrade yargs from 15.3.0 to 15.3.1 ([bafa831](bafa831)) * upgrade yargs from 15.3.0 to 15.3.1 ([9df01ed](9df01ed))
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Paying it forward and pushing my changes out for all to see/use before I archive my branch.
This does include a lot of
@randy.tarampi/*repo specific things, but those should be easy enough to fix or ignore if these changes get picked up. This PR's more for visibility than anything anyways.Other than a whole host of upgrades, most of the functional changes are listed in the
CHANGELOG.