You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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 ?
Reacted by commarla, Romain Gautier, Celestin Prud'homme, Ronny Roeller, Pieter Oliver and Julian Meyer
@austencollins could you help on this issue? If you can update the NPM_TOKEN value with a new valid one in this repository secrets, that'd be perfect!
Thanks
@Mmarzex, I just updated a few actions on test and build definition workflows as well as stepping up node version.
I just opened a pull request with the changes: #93
Activity
fredericbarthelet commentedon Aug 20, 2023
@ac360 could you help on the aforementioned issue :) ?
fcappi commentedon Sep 13, 2023
Any updates about this issue?
guillaume-le-fur commentedon 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 commentedon Nov 16, 2023
Any updates on this?
Node 20 lambda runtime has just been released and ppl will want
type AwsLambdaRuntimeupdated from serverless.IdrissMahjoubi commentedon Nov 25, 2023
Any updates on this build issue ? I need to use the
invokeModeconfig attributefredericbarthelet commentedon Nov 25, 2023
@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 :)
fredericbarthelet commentedon Jan 8, 2025
@austencollins could you help on this issue? If you can update the NPM_TOKEN value with a new valid one in this repository secrets, that'd be perfect!
Thanks
Mmarzex commentedon Jan 8, 2025
@fredericbarthelet Token has been updated, sorry about that.
fredericbarthelet commentedon Jan 8, 2025
Great! Thanks @Mmarzex for your help! Could you run the workflow or give me back rights on this repo to run the workflow?
Mmarzex commentedon Jan 8, 2025
@fredericbarthelet Looks like it isn't working, https://github.com/serverless/typescript/actions/runs/12678920352/job/35337545351
fredericbarthelet commentedon Jan 8, 2025
@Mmarzex, I just updated a few actions on test and build definition workflows as well as stepping up node version.
I just opened a pull request with the changes: #93
Installing dependencies seem to go like a charm: https://github.com/fredericbarthelet/serverlesstypescript/actions/runs/12679397766/job/35339008893. However, I'm blocked at
npx sls schemastep as I don't have a valid license key. Can I suggest you had a key from Serverless team as a secret in this repo under nameSERVERLESS_LICENSE_KEY?RishikeshDarandale commentedon Jan 9, 2025
@Mmarzex , Can you please merge #93 and add either
SERVERLESS_ACCESS_KEYorSERVERLESS_LICENSE_KEY?RishikeshDarandale commentedon Jan 10, 2025
@Mmarzex , can we please do this today?
RishikeshDarandale commentedon Jan 13, 2025
Going ahead with patch-package functionality for using
serverlessv4 feature, until #93 and this gets merged.index.d.ts) from feat: update the schema for serverless v4 #92 tonode_modules/@serverless/typescript/index.d.tspatch-packagewithnpm i patch-packagenpx patch-package @serverless/typescripts"postinstall": "patch-package"to your scripts inpackage.json