Updating extensions

010101

I searched the forum here and the answer seems to be no. But just in case. Any way with composer to update ONLY all extensions with a new version? So don’t update symphony or other things. Just extensions.

Ralkage

010101 you can simply specify the package you want to update specifically 🙂 each extension discussion should have simple update commands listed as well and you should also be able to add multiple extensions to a one line command as well like so:

composer update vendor-1/extension-1 vendor-2/extension-2 vendor-3/extension-3

clarkwinkelmann

Also see the --root-reqs option of composer update:

      --root-reqs                Restricts the update to your first degree dependencies.

010101

clarkwinkelmann Cool! I’ll have to try this. If it works well it might need to be a well advertised way for people to update all extensions in one command (added to documentation) since we don’t have any type of alert telling us an extension has a new version.

clarkwinkelmann

It's still important to update dependencies of dependencies as well.

composer update <extension package> is usually the best option if you want to update select packages.

Adding the --with-all-dependencies flag will also update all dependencies required by the given packages

composer update is useful if you want to update everything that can be updated, but it's best to run that command on a local environment, test everything went well, then deploying Flarum via the lock file to reduce memory consumption and runtime.

composer show --direct --outdated can be used to show all extensions with an update available.

010101

clarkwinkelmann You are the best! @Ralkage too. But, Clark is freaking amazing!! Neither of you better ever leave the Flarum community. Please.

fakruzaruret

clarkwinkelmann composer update does nor work nicely.

I used composer show --direct --outdated command so there are several extensions which have updates but I cant update all ofthem via composer update command

[deleted]

010101 I've got to agree with this, but how could you leave out @datitisev, @tankerkiller125 and @askvortsov 😁 who have been equally awesome (for me, anyway, and I know that to be the case with others)

And who of course could forget our resident "ninja" @luceos ??

Seriously guys - take a bow. This product wouldn't be what it is today without core devs like yourselves.

If nobody else likes this comment, you all have swinging rocks for hearts 🤭 (just kidding).

I'm immensely proud to be only a small fish in this much larger ecosystem and community.

tankerkiller125

fakruzaruret This is because those extensions updates are considered "major" by composer. By default composer does not auto update to major versions. You'll need to run something like composer install fof/user-bio 0.2.0 in order to force it to update to the major version.

Also huge thanks for the compliments [deleted] we all try our hardest.

fakruzaruret

tankerkiller125 thank you very much. This is valuable information.

clarkwinkelmann

tankerkiller125 it's composer require <package> 😉

It also works with `composer install <package> but Composer documentation says to avoid it and I wouldn't be surprised if this has been dropped in Composer 2.0.

tankerkiller125

fakruzaruret As a note there is probably a better way to do it. That's just the method that I usually end up using.

tankerkiller125

clarkwinkelmann I'm always confusing npm and composer 🤦

pkernstock

I'm also wondering what the intended way of updating extensions is. Unfortunately the doc page at https://docs.flarum.org/update.html just points towards each release-specific announcement for updating.

So far I'm using following parameters together with composer to update extensions and its dependencies:
$ composer update --prefer-dist --no-dev -a --with-all-dependencies

So I'm wondering if that's an official and safe way updating everything?

luceos

pkernstock I've recently adopted the rather simplistic method of setting the constraint of all extensions to * counter intuitively. Then it's just a matter of running composer update. The drawback here is you never know what extension major version you download. However it's always compatible (or is supposed to be) with the flarum core version in use.