Was anyone able to pin a specific Serverless version by adding it as dependency in package.json, as mentionned in documentation. (I prefer this way instead of fixing the version in each micro-service serverless.yml)

Hey @Maxime, yup the dependency way is now the recommended way to pin the SLS version. Did it work for you?

Yep, that’s what I use normally

Not sure if it works, as when I'm pinning the version in serverless.yml, I can see it in the 'Init' section (screenshot), which is not the case when I pin it in package.json

I tried this :

{
  "name": "event-process",
  "description": "",
  "version": "0.1.0",
  "dependencies": {},
  "devDependencies": {
    "serverless-latest-layer-version": "^2.1.1",
    "serverless-plugin-epsagon": "^1.12.2",
    "serverless": "^2.27.0"
  }
}

One of our services needed custom event bus triggers and many of them are available only in

2.27.0+

and initially default seed cicd was not working due to low serverless version. Then i added this in package json and it works now perfectly

Thanks for your feedback @Sourav Sarkar. Can you please let me know which Serverless version you see in the 'Init' section of the Seed build logs?

it was a very low version 2.1x.x as per I remember, i am sure that the solution worked as my features are only available in the mentioned versions