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

Publish to NPM failed #81

Open
fredericbarthelet opened this issue Aug 20, 2023 · 6 comments
Open

Publish to NPM failed #81

fredericbarthelet opened this issue Aug 20, 2023 · 6 comments

Comments

@fredericbarthelet
Copy link
Contributor

Github action handling publishing of @serverless/typescript package to NPM currently fails.
Last published version is 3.30.1 - versioning of this package follows serverless main package versions.

Failed job : https://github.com/serverless/typescript/actions/runs/5819791268/job/16047655020

I believe this could be due to changes made on serverless NPM team and currently used Github action secret NPM_TOKEN might not be valid anymore. Could someone from serverless team help here ?

@fredericbarthelet
Copy link
Contributor Author

@ac360 could you help on the aforementioned issue :) ?

@fcappi
Copy link

fcappi commented Sep 13, 2023

Any updates about this issue?

@guillaume-le-fur
Copy link

guillaume-le-fur commented Sep 20, 2023

Edit : My bad, I hadn't read your comment about the token, you can disregard my comment 😅

Hello @fredericbarthelet,

Apparently, npm can throw 404 when publishing if you are not logged in.

Are you sure the token you use when publishing is still valid? See here. Maybe your token has expired?

Ps : Thank you for you (amazing) work on this package 🙂

@herebebogans
Copy link

Any updates on this?

Node 20 lambda runtime has just been released and ppl will want type AwsLambdaRuntime updated from serverless.

@IdrissMahjoubi
Copy link

IdrissMahjoubi commented Nov 25, 2023

Any updates on this build issue ? I need to use the invokeMode config attribute

@fredericbarthelet
Copy link
Contributor Author

@ac360 could you help on this issue and update the NPM_TOKEN value with a valid one in this repository secrets ? Thanks a lot for your help :)

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

5 participants