Problem/Motivation

I'm updating my site but the Tagcloud module doesn't update with core and dependencies.

Steps to reproduce

1. Review available updates at /admin/reports/updates. This shows that I have 2.0.9 currently installed but 2.0.10 is available.
2. Update Drupal with all dependencies using composer: composer update "drupal/core-*" -W
3. Since Tagcloud doesn't update with that command, I have to do it by itself.
composer update drupal/tagcloud -W --dry-run

Proposed resolution

Module should update with the core-* & dependencies update in step 2 above. Tagcloud is not the only such module ... some update with core-* & dependencies but some don't. Is there something I should do differently to make this happen? Thanks.

Remaining tasks

User interface changes

API changes

Data model changes

Comments

leeksoup created an issue. See original summary.

grask0’s picture

grask0 commented
Status: Active » Fixed

Hey @leeksoup,

There are actually two separate issues here:

1. Incorrect machine name
The module’s machine name is tagclouds, not tagcloud.
So when running Composer commands, you should use:

composer update drupal/tagclouds -W

Using drupal/tagcloud won’t work because that package doesn’t exist.

2. Version constraint in composer.json
In your composer.json, the Tagclouds module is probably pinned to a fixed version, like:

"drupal/tagclouds": "2.0.9"

That means Composer will never update it beyond 2.0.9, even if 2.0.10 is available.
To allow updates automatically, you should change it to:

"drupal/tagclouds": "^2.0"

Then, when you run the update command, it will update to the latest compatible 2.x release.

Module should update with the core- & dependencies update in step 2 above.*

Not necessarily.
The command

composer update "drupal/core-*" -W

only updates Drupal core packages (those starting with drupal/core-*).
Contributed modules like Tagclouds are not included unless you explicitly update them or run:

composer update "drupal/*" -W

So the module is not expected to update automatically with the core update - this is normal Composer behavior, not a module issue.

Now that this issue is closed, please review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, please credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.