serverless: Error "Could not find a valid version to run"

Issue description

Getting “Could not find a valid version to run” when running any command with serverless.

Was using mac 13.5, then tried updating to Sequoia, but didn’t change anything.

Serverless installed version 4.4.4

Reproduction:

npm i -g serverless
serverless

Context

No response

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 15 (6 by maintainers)

Most upvoted comments

Same here, even with frameworkVersion: 4.4.0 pinned in serverless.yml and ~/.serverless/releases/4.4.0 already present on my machine. Seems like a critical ops issue on the Serverless end.

Is it time to consider abandoning auto-updates yet? It’s caused us nothing but pain and we don’t want it.

looks like we’re back @austencollins thanks for the fast turn around

@austencollins We love using your framework and have hundreds of different deployments with your library, we love what you’re doing as it simplifies a difficult problem for us. But is there any particular reason your testing (CICD integration testing or e2e maybe?) didn’t pick this up? We like to use latest version in our docker pipelines for deployments, so this was quite disruptive to our ones migrated to your paid v4 offerings.

@NicoHinderling The Framework version locally on your machine is fine. But on initialization, the Framework checks our Releases API to look for new releases, ensure the current version is stable, ensure the current version has no security issues, etc. Unfortunately, we pushed a minor bug to our Releases API and the CLI did not handle that error scenario correctly. We fixed the API and identified where to improve the CLI in this case, letting it fall back to using the target version without qualms.

Thanks for reporting @viniciushvsilva. We’re looking into this now.