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

Upgrade to node 20 #653

Open
AlexJetplan opened this issue Feb 4, 2025 · 6 comments
Open

Upgrade to node 20 #653

AlexJetplan opened this issue Feb 4, 2025 · 6 comments

Comments

@AlexJetplan
Copy link

Node 18 is going to be deprecated and decommissioned by GCP.

Are there any plans to upgrade the version for the extension?

Image

@krishsatya
Copy link

krishsatya commented Feb 5, 2025

That would be great, but I wouldn't hold my breath. Development on this extension has been inactive for some time now.

@AlexJetplan
Copy link
Author

That would be great, but I wouldn't hold my breath. Development on this extension has been inactive for some time now.

Yes, I have gathered as much. Very unfortunate. We have decided as a team to rebuilt the functionality in house now :/

Thanks for the heads up!

@androng
Copy link

androng commented Feb 9, 2025

Solution is to change this line to "node": "20"

@timmolter
Copy link

Are there any known forks of this project that are keeping things up to date?

@swiing
Copy link

swiing commented Feb 16, 2025

That would be great, but I wouldn't hold my breath. Development on this extension has been inactive for some time now.

When the extension was handed over to invertase, the following comment was made, quote:

The Invertase team is committed to addressing this extension’s existing issues and providing long-term maintenance.

Looks like that was a very weak commitment, to say the least.

We’re here if you have any questions or concerns.

So question to @paulasjes-stripe is: is stripe aware of the lack of maintenance, and is there any plan for improvement, or should we move to something different?

@Andre1992
Copy link

Andre1992 commented Mar 9, 2025

Solution is to change this line to "node": "20"

I might also add that dont forget to change the runtime aswell when changing the package.json version.

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

No branches or pull requests

6 participants