Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
The composer.json includes some dependencies, but the versions specified don't match the versions available in the repos that are included in the composer.json file.
The dev-branchname convention only works with repos of type vcs, where this should work with packagist.drupal-composer.org.
Comments
Comment #2
BerdirThanks. I've just released token alpha2, ctools already had a new release, which means we no longer require their dev versions, while changing this can you update the patch to remove that?
Comment #3
mikey_p CreditAttribution: mikey_p commentedI think this is what you're looking for, although token token 8.x-1.0-alpha2 doesn't seem to be on Drupal Packagist yet.
Comment #4
Berdirdoesn't that mean *only* exactly those releases? Can't we say at least that or anything that's newer?
Comment #5
Berdirwebflo: berdir: i think ~8.1.0-alpha2 should work. it means =>8.1.0-alpha2, <8.2.0
Comment #6
mikey_p CreditAttribution: mikey_p commentedI think in composer lingo that would be anything up to 9.0.0 wouldn't it?
Comment #7
mikey_p CreditAttribution: mikey_p commentedAhh, I read that wrong, ~ is "allow next major release" which means that if a major.minor.patch is specified, then only the least significant item can be updated. (i.e. patch)
Comment #8
BerdirThanks.
Comment #13
Berdir