bower-asset/jquery 3.7.1 missing again
Please provide your composer.json if appropriate.
Similar to https://github.com/hiqdev/asset-packagist/issues/167
Problem 1
- Root composer.json requires bower-asset/jquery == 3.7.1.0 (exact version match), found bower-asset/jquery[dev-main, 1.0-alpha1, ..., 1.12.4, 2.0.0-beta1, ..., 2.2.4, 3.0.0-alpha1, ..., 3.6.4] but these do not match your constraint and are therefore not installable. Make sure you either fix the constraint or avoid updating this package to keep the one present in the lock file (bower-asset/jquery[3.7.1]).
https://asset-packagist.org/package/bower-asset/jquery
For reference: https://github.com/yiisoft/yii2/issues/20067
Adding my +1 to this.
FYI, same problem with bower-asset/inputmask. It downgrades from 5.0.9 to 5.0.8. Fetching updates from bower then shows the newest releases again, although only for a short amount of time.
@SilverFire @hiqsol Could you look into that, this is creating serious "downgrading problems"
Hi. Started my investigation on this issue.
@SilverFire Thank you in advance.
Maybe for the future, create a monitoring Request for https://asset-packagist.org/package/bower-asset/jquery which looks for the string 3.7.1.
Just out of curiosity, how do you make a version like jquery:3.7.1 available as bower package if it has no bower.json
@SilverFire Any news regarding this, anything we could help you with?
This is really blocking all of our work and it's not even possible to switch back to the plugin, since it's not compatible with composer API v2.
https://github.com/fxpio/composer-asset-plugin/issues/334
Possible workaround: we recently switched packages pulling from bower-asset/ to source from npm-asset/ instead, where jQuery 3.7.1 is not missing: https://asset-packagist.org/package/npm-asset/jquery. Seems to work even with jQuery as an indirect dependency.
Before:
"require": {
"bower-asset/datatables.net": "^1.13.11"
}
After:
"require": {
"npm-asset/datatables.net": "^1.13.11"
}
But jQuery is a Core Package, how do you Deal with that?
As a temporary workaround you can define package directly in composer.json
https://getcomposer.org/doc/05-repositories.md#package-2 https://stackoverflow.com/a/49947784/5812455