# Serverless 3 & 4 together

**URL:** https://forum.serverless.com/t/serverless-3-4-together/20424
**Category:** Serverless Framework
**Created:** [August 13, 2024, 10:45am UTC](https://forum.serverless.com/t/serverless-3-4-together/20424 "2024-08-13T10:45:00Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![TomC](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.serverless.com/tomc/32/4002_2.png) [@TomC](https://forum.serverless.com/u/TomC)
#### Post date: [August 13, 2024, 10:45am UTC](https://forum.serverless.com/t/serverless-3-4-together/20424/1 "2024-08-13T10:45:00Z")

</div>

I’m sure I can’t be the only one who has a lot of Sls v3 projects, that we don’t want to upgrade to v4 right now.

If I install Sls v4 ( [Setting Up Serverless Framework With AWS - Setting Up Serverless Framework With AWS](https://www.serverless.com/framework/docs/getting-started) installs a global `npm` package ), will I still be able to deploy the old v3 projects ? They all have `framework: '3'` in their top level `serverless.yml`

Basically - will the v4 CLI fall back to v3 semantics if the project says to ?

---

<div class="post-metadata">

### Author: ![TomC](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.serverless.com/tomc/32/4002_2.png) [@TomC](https://forum.serverless.com/u/TomC)
#### Post date: [August 13, 2024, 12:27pm UTC](https://forum.serverless.com/t/serverless-3-4-together/20424/2 "2024-08-13T12:27:25Z")

</div>

I guess not

```auto
$ sls info --aws-profile foo-bar-boo --stage dev 

✖ The Serverless version (4.1.21) does not satisfy the "frameworkVersion" (3) in serverless.yml
ServerlessError2: The Serverless version (4.1.21) does not satisfy the "frameworkVersion" (3) in serverless.yml

```

So the appropriate action is to change every (!) project’s framework version at once, and push updated tools to everyone.

Eww ?

What’s the timeline for the official Chocolatey ( [Chocolatey Software | serverless](https://community.chocolatey.org/profiles/serverless) ) packages being updated ? We’d need to make sure we had updated .yml files before then.

[workaround : `sudo npm i serverless@3 -g` to revert to v3]

[aside: no docs in [serverless.yml Reference - Serverless Framework - AWS Lambda Guide - Serverless.yml Reference](https://www.serverless.com/framework/docs/providers/aws/guide/serverless.yml) around `frameworkVersion` itself, so dunno why `Serverless version (4.1.21) does not satisfy the "frameworkVersion" (3.x || 4.x) in serverless.yml` either ]

---

<div class="post-metadata">

### Author: ![ChristopherB](https://avatars.discourse-cdn.com/v4/letter/c/3d9bf3/32.png) [@ChristopherB](https://forum.serverless.com/u/ChristopherB)
#### Post date: [January 22, 2025, 8:37am UTC](https://forum.serverless.com/t/serverless-3-4-together/20424/3 "2025-01-22T08:37:16Z")

</div>

Unbelievable that there isn’t an official response on this.

Thanks for your comment, I downgraded for now to 3 and don’t plan on switching unless forced. This is ridiculous and their new model is a joke
