Skip to content

Support modern node, amongst other things#4

Open
randytarampi wants to merge 387 commits into
PeerJ:masterfrom
randytarampi:master
Open

Support modern node, amongst other things#4
randytarampi wants to merge 387 commits into
PeerJ:masterfrom
randytarampi:master

Conversation

@randytarampi

Copy link
Copy Markdown
Contributor

Paying it forward and pushing my changes out for all to see/use.

And y'know, also building up a list of things to point at while I hunt for jobs. 🤣

This should resolve #2 and #3 by adding an updateDefinitions lambda that handles all the definitions work.

More changes detailed in the CHANGELOG.

greenkeeper Bot and others added 30 commits July 1, 2019 12:34
chore(greenkeeper): Update eslint-plugin-import
chore(greenkeeper): Update gulp-eslint
chore(greenkeeper): Update del
[Snyk] Fix for 1 vulnerable dependencies
chore(greenkeeper): Update babel7
[Snyk] Fix for 1 vulnerable dependencies
[skip ci]

## [2.0.5](v2.0.4...v2.0.5) (2019-07-05)

### Bug Fixes

* .snyk, package.json & package-lock.json to reduce vulnerabilities ([194bf53](194bf53))
* .snyk, package.json & package-lock.json to reduce vulnerabilities ([fa57e5a](fa57e5a))
* Apply Synk patch for SNYK-JS-LODASH-450202. ([7b1f094](7b1f094))
* Apply Synk patch for SNYK-JS-LODASH-450202. ([655abfc](655abfc))
…support node@10.

BREAKING CHANGE: Really, this is more about dropping support for node@8, but AWS is disallowing creation of node@8 lambdas today anyways, per https://docs.aws.amazon.com/lambda/latest/dg/runtime-support-policy.html.

Also, we'll also need to have real virus definitions on hand as the rewrite of `clamscan` dropped the testing mode. Which is unfortunate.
Merge pull request #65 from randytarampi/greenkeeper/initial
[skip ci]

# [3.0.0](v2.0.5...v3.0.0) (2020-01-07)

### Features

* **package:** Blindly upgrade our dependencies for the new year and support node@10. ([9c9cc82](9c9cc82))

### BREAKING CHANGES

* **package:** Really, this is more about dropping support for node@8, but AWS is disallowing creation of node@8 lambdas today anyways, per https://docs.aws.amazon.com/lambda/latest/dg/runtime-support-policy.html.

Also, we'll also need to have real virus definitions on hand as the rewrite of `clamscan` dropped the testing mode. Which is unfortunate.
…ots. Be practical, be candid, be yourself. 🤷‍♂️
…e.yml and other dead CI configs. They're gone. Let them go. 🪦

Also: fix .gitignore gaps (test-results.xml, .nyc_output/, *.iml, .idea/, lerna-debug.log) to match dotfiles categorization, move PR template to .github/, and document reactShim.js polyfills in LIMITATIONS.md.
…h cacheable targets + --since for affected builds. Also: widen eslint-plugin-import peer range to fix the YN0060 warnings. 🤞
… CI caching — because we paid for those upgrades, might as well use them. 💰
…-commit hooks: because trust is good, control is better. 🔒
…s dead, long live Actions. 👑

- me: release.yml (lerna publish + GitHub release), deploy.service.yml (AWS Lambda), deploy.pages.yml (prd tag deploys)
- pwa/pseudoimage/pseudolocalize/lwip: release.yml (semantic-release with OIDC trusted publishing)
- slamscan: CI updated, no release (private package)
… The package is deprecated, the action is the future. 📊
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Embedding database virus definition in the Lambda function

4 participants