Skip to content
This repository has been archived by the owner on Jun 27, 2019. It is now read-only.

Bump versions of dependencies and Node.js #328

Merged
merged 5 commits into from
Jun 19, 2018
Merged

Bump versions of dependencies and Node.js #328

merged 5 commits into from
Jun 19, 2018

Conversation

kola-er
Copy link
Contributor

@kola-er kola-er commented Jun 13, 2018

Add support for Node.js 8.10.

@kola-er kola-er changed the title WIP: Bump versions of dependencies and Node.js Bump versions of dependencies and Node.js Jun 14, 2018
@kola-er kola-er requested a review from xavdid June 14, 2018 00:46
Copy link
Contributor

@xavdid xavdid left a 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".
Copy link
Contributor

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"
Copy link
Contributor

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`
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This way? @xavdid

Copy link
Contributor

@xavdid xavdid Jun 18, 2018

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.

@kola-er
Copy link
Contributor Author

kola-er commented Jun 19, 2018

@xavdid Please final review. Thanks.

Copy link
Contributor

@xavdid xavdid left a 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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants