<p>Yes, you can update to any version you want through Composer. Either manually edit the version of <code>craftcms/cms</code> in your <code>composer.json</code>, then run <code>composer update</code>, or use <code>composer require</code> to set the version. You may need to update other dependencies as well – for example, update some plugins to work with the installed Craft version. In this case, edit the <code>composer.json</code> and set all plugins / other dependencies to compatible versions, then run <code>composer update</code>. Composer will tell you if there are any version conflicts that need fixing.</p>
<p>The only thing to keep in mind is that after updating Craft or any plugins through Composer, you need to run any pending migrations manually (and to be safe, apply any pending project config changes):</p>
<ul>
<li><code>php craft migrate/all</code></li>
<li><code>php craft project-config/apply</code></li>
</ul>
<p>Two great articles on this topic:</p>
<ul>
<li><a href="https://nystudio107.com/blog/updating-craft-cms-without-headaches" rel="nofollow noreferrer">Updating Craft CMS without headaches</a></li>
<li><a href="https://nystudio107.com/blog/composer-for-the-rest-of-us" rel="nofollow noreferrer">Composer for the rest of us</a></li>
</ul>

CC BY-SA 4.0
2023-04-11T14:35:11.483Z
Thank you very much for the speedy response.  I've 'adjusted' composer before, but since I was so far behind on my updates, I didn't want to get into trouble. ;-)
Unlimited
CC BY-SA 4.0
2023-04-11T15:01:24.397Z
@Unlimited Managing the Composer files manually is totally normal and expected! In fact, you'll have to do that anyway if you have any dependencies that aren't Craft plugins, since the Craft updater won't touch those. So its a good idea to get comfortable interacting with Composer directly. If you issue is solved, don't forget to mark the answer as accepted. Thanks!
MoritzLost
CC BY-SA 4.0
2023-04-11T12:37:40.287Z
2023-04-11T12:37:40.287Z
MoritzLost
<p>We have a site that has been in production for a while and finally have been given the task of upgrading to Craft 4.  We are at Craft Pro 3.4.29.1.  Can I upgrade the site in stages? i.e. from 3.49 to 3.5, then 3.6, etc?  I'm concerned about upgrading from such an old version.</p>
<p>Maybe setting the Craft version to 3.5 in composer.json and running the update with native composer instead of the craft cli?</p>
<p>Thanks!!</p>
<p>Duane</p>

<craft3><upgrades>
Upgrading from 3.49 to Craft 4, Incrementally
# Upgrading from 3.49 to Craft 4, Incrementally

(Asked by: username_0 on 2023-04-10)

We have a site that has been in production for a while and finally have been given the task of upgrading to Craft 4. We are at Craft Pro 3.4.29.1. Can I upgrade the site in stages? i.e. from 3.49 to 3.5, then 3.6, etc? I'm concerned about upgrading from such an old version.

Maybe setting the Craft version to 3.5 in composer.json and running the update with native composer instead of the craft cli?

Thanks!!

Duane

**Tags:** craft3, upgrades


---

## 1 answers

### Answer by username_1 on 2023-04-11. Score: 3

Yes, you can update to any version you want through Composer. Either manually edit the version of `craftcms/cms` in your `composer.json`, then run `composer update`, or use `composer require` to set the version. You may need to update other dependencies as well – for example, update some plugins to work with the installed Craft version. In this case, edit the `composer.json` and set all plugins / other dependencies to compatible versions, then run `composer update`. Composer will tell you if there are any version conflicts that need fixing.

The only thing to keep in mind is that after updating Craft or any plugins through Composer, you need to run any pending migrations manually (and to be safe, apply any pending project config changes):

* `php craft migrate/all`
* `php craft project-config/apply`

Two great articles on this topic:

* [Updating Craft CMS without headaches](https://nystudio107.com/blog/updating-craft-cms-without-headaches)
* [Composer for the rest of us](https://nystudio107.com/blog/composer-for-the-rest-of-us)

> **Comments:**
> **username_0**: Thank you very much for the speedy response.  I've 'adjusted' composer before, but since I was so far behind on my updates, I didn't want to get into trouble. ;-)  
> **username_1**: @username_0 Managing the Composer files manually is totally normal and expected! In fact, you'll have to do that anyway if you have any dependencies that aren't Craft plugins, since the Craft updater won't touch those. So its a good idea to get comfortable interacting with Composer directly. If you issue is solved, don't forget to mark the answer as accepted. Thanks!  

---

