Skip to content
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update documentation related to the latest AWS Lambda runtime nodejs20.x #5674

Merged
merged 4 commits into from
Feb 29, 2024

Conversation

jharrell
Copy link
Member

Fixes #5524

Copy link

vercel bot commented Feb 21, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Feb 29, 2024 2:18pm

@jharrell jharrell requested review from janpio and mhessdev February 21, 2024 18:44
Copy link
Contributor

This PR changes the following pages (Vercel Preview Deploy links):

Changed Vercel links

(Note that links will only be valid after Vercel preview deploy succeeded)

@jharrell jharrell self-assigned this Feb 21, 2024
Copy link
Contributor

This PR probably requires the following redirects to be added to vercel.json:

  • This PR does not change any pages in a way that would require a redirect.

Copy link
Contributor

@janpio janpio left a comment

Choose a reason for hiding this comment

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

Looks fine.

Do we maybe want to document it in a way already that we do not have to updated again when Node 20 becomes the default, or more common, so to present the options more equal and maybe the more modern one first?

@jharrell
Copy link
Member Author

Thanks @janpio , I made some changes making tabs where relevant and Node 20 the default where not. Hopefully that matches your expectation?

Copy link
Contributor

@janpio janpio left a comment

Choose a reason for hiding this comment

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

Looks good 👍

@janpio
Copy link
Contributor

janpio commented Feb 22, 2024

Actually: Does this also apply to the ARM Lambda? There it is still 1.0.x exclusively.
image

@janpio janpio self-requested a review February 22, 2024 17:26
@jharrell jharrell merged commit 7124ef4 into main Feb 29, 2024
7 checks passed
@jharrell jharrell deleted the jharrell/issue5524 branch February 29, 2024 14:31
@janpio
Copy link
Contributor

janpio commented Mar 1, 2024

Actually: Does this also apply to the ARM Lambda? There it is still 1.0.x exclusively. image

What is the answer to this question?

@jharrell
Copy link
Member Author

jharrell commented Mar 1, 2024

@janpio I don't know if this applies to ARM64 architecture. I don't think it does, but I will need to try it out.

@janpio
Copy link
Contributor

janpio commented Mar 1, 2024

Please do, otherwise the information in our docs is now incomplete.

ankur-arch pushed a commit that referenced this pull request Mar 4, 2024
…0.x (#5674)

* Update documentation related to the latest AWS Lambda runtime nodejs20.x
Fixes #5524

* change default to be node 20+

* Update content/200-orm/500-reference/300-environment-variables-reference.mdx

Co-authored-by: Jan Piotrowski <[email protected]>
ankur-arch added a commit that referenced this pull request Mar 11, 2024
* feat: add pulse error reference

* enhance: change to known limitations and enhance reasoning for database event being discarded

* feat: add section on replication slots

* feat: add replication slot submission image

* feat: add faq for pulse regarding throughput

* fix: fix indentation

* fix: update pulse information regarding ssl and support

* fix: fix indentation and prune content

* feat: add database providers

* fix: broken link (#5684)

* update docs about relation joins to include mysql (#5686)

* Update documentation related to the latest AWS Lambda runtime nodejs20.x (#5674)

* Update documentation related to the latest AWS Lambda runtime nodejs20.x
Fixes #5524

* change default to be node 20+

* Update content/200-orm/500-reference/300-environment-variables-reference.mdx

Co-authored-by: Jan Piotrowski <[email protected]>

* feat: add example projects

* Optimised images with calibre/image-actions

* fix: indentation and add examples

* fix: add indendation, clear references of slack and update product naming

* fix: correct spelling for unreachability

* fix: remove grammatical errors

* fix: remove limitation

* feat: add replication slot and neon docs

* Optimised images with calibre/image-actions

* fix: fix word

* feat: remove early access

* feat: add additional section on pulse

* enhance: fix indentation

* Update content/400-pulse/100-what-is-pulse.mdx

Co-authored-by: Luan van der Westhuizen <[email protected]>

* Update content/400-pulse/100-what-is-pulse.mdx

Co-authored-by: Luan van der Westhuizen <[email protected]>

* Update content/400-pulse/100-what-is-pulse.mdx

Co-authored-by: Luan van der Westhuizen <[email protected]>

* Update content/400-pulse/100-what-is-pulse.mdx

Co-authored-by: Luan van der Westhuizen <[email protected]>

* enhance: getting started definition of Pulse

* enhance: known limitations section

* enhance: update concepts page

* enhance: reshuffle faq section

* fix: broken summary tag

* feat: restructure getting started page and divide setup

* feat: add more content to waht is pulse

* feat: restructure content

* Optimised images with calibre/image-actions

* feat: refine what is pulse

* feat: refine pulse further

* feat: api reference  pulse

* enhance: refine content a bit further

* fix: spelling mistakes and roken links

---------

Co-authored-by: Nikolas <[email protected]>
Co-authored-by: Jon Harrell <[email protected]>
Co-authored-by: Jan Piotrowski <[email protected]>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: Luan van der Westhuizen <[email protected]>
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.

Update documentation related to the latest AWS Lambda runtime nodejs20.x
3 participants