-
Notifications
You must be signed in to change notification settings - Fork 60
Bump versions of dependencies and Node.js #328
Conversation
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.
once you make the small changes, good to go
CHANGELOG.md
Outdated
### schema | ||
### core | ||
|
||
* (**BREAKING**) Apps with dependency zapier-platform-core=">=7.0.0" run only on Node.js `v8.10.0` in AWS Lambda. If you need to continue running on Node.js `v6.10.3`, use zapier-platform-core="<=6.1.0". |
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.
this is generated automatically later, can revert.
README-source.md
Outdated
@@ -1179,7 +1179,7 @@ This makes it pretty straightforward to integrate into your testing interface. I | |||
```yaml | |||
language: node_js | |||
node_js: | |||
- "6.10.2" | |||
- "8.10.0" |
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.
this should be LAMBDA_VERSION
so it gets autofilled.
README-source.md
Outdated
@@ -1179,7 +1179,7 @@ This makes it pretty straightforward to integrate into your testing interface. I | |||
```yaml | |||
language: node_js | |||
node_js: | |||
- "6.10.2" | |||
- `LAMBDA_VERSION` |
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.
This way? @xavdid
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.
oh sorry, I totally spaced on this. it would be "LAMBDA_VERSION"
since I believe it's just a string replace.
@xavdid Please final review. Thanks. |
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.
sweet!
I noticed that the eslint error for the next.js code is a parse error (not an unsupported feature) but I think it accomplishes the same basic task. I think it accomplishes the same basic idea and with any luck, we'll be able to take it out eventually.
Add support for Node.js 8.10.