- Notifications
You must be signed in to change notification settings - Fork396
edits to Destination Insert Functions#7908
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
| This upgrade keeps your runtime current with industry standards. Based on the[AWS Lambda](https://docs.aws.amazon.com/lambda/latest/dg/lambda-runtimes.html){:target="_blank"} and[Node.js](https://nodejs.org/en/about/previous-releases){:target="_blank"} support schedule, Node.js v16 is no longer in*Maintenance LTS*. Production applications should only use releases of Node.js that are in*Active LTS* or*Maintenance LTS*. | ||
| All new functions will useNode.jsv18 starting March 26, 2024. | ||
| For existing functions, this change automatically occurs as you update and deploy an existing function. Segment recommends that you check your function post-deployment to ensure everything's working. Your function may face issues due to the change in syntax between differentNode.jsversions and dependency compatibility. |
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.
| For existing functions, this change automatically occurs as you update and deploy an existing function.Segment recommends that you check your function post-deployment to ensure everything's working. Your function may face issues due to the change in syntax between different Node.js versions and dependency compatibility. | |
| For existing functions, this change automatically occurs as you update and deploy an existing function.We recommend that you check your function post-deployment to ensure everything's working. Your function may face issues due to the change in syntax between different Node.js versions and dependency compatibility. |
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.
No real changes! Are we sticking to the Seg style guide or applying Twilio rules yet? (I made a few Twilio-esque suggestions)
Co-authored-by: Sharon Adewusi <sadewusi@twilio.com>
Co-authored-by: Sharon Adewusi <sadewusi@twilio.com>
d713849 intodevelopUh oh!
There was an error while loading.Please reload this page.
Thank you for your contribution! Your pull request is merged, but may take a day or two to appear on the site. |
Proposed changes
edits to Destination Insert Functions for the Segment Docs Audit
Merge timing
Related issues (optional)