Update flysystem usage after upgrade #690
Annotations
2 errors and 1 warning
CI
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Root composer.json requires oat-sa/extension-tao-testqti dev-d9155f1b5c1ded146ae389e710be88d8dacc8f67 as v99.99.99 -> satisfiable by oat-sa/extension-tao-testqti[dev-d9155f1b5c1ded146ae389e710be88d8dacc8f67].
- league/flysystem-memory[1.0.0, ..., 1.0.x-dev] require league/flysystem ~1.0 -> satisfiable by league/flysystem[1.0.0-alpha1, ..., 1.x-dev].
- oat-sa/extension-tao-testqti dev-d9155f1b5c1ded146ae389e710be88d8dacc8f67 requires league/flysystem ^3.0 -> satisfiable by league/flysystem[3.0.0, ..., 3.x-dev].
- oat-sa/extension-tao-testqti dev-d9155f1b5c1ded146ae389e710be88d8dacc8f67 requires oat-sa/generis >=15.36.4 -> satisfiable by oat-sa/generis[v15.36.4, v15.36.5, v15.37.0, v15.38.0, 9999999-dev].
- oat-sa/generis[dev-master, v15.31.0, ..., v15.38.0] require league/flysystem-memory ~1.0 -> satisfiable by league/flysystem-memory[1.0.0, 1.0.1, 1.0.2, 1.0.x-dev].
- Conclusion: don't install league/flysystem 1.0.12 (conflict analysis result)
- Conclusion: don't install league/flysystem 1.0.28 (conflict analysis result)
- Conclusion: don't install league/flysystem 1.0.29 (conflict analysis result)
- Conclusion: don't install league/flysystem 1.0.46 (conflict analysis result)
- Conclusion: don't install league/flysystem 1.0.70 (conflict analysis result)
- Conclusion: don't install league/flysystem 1.1.10 (conflict analysis result)
- Conclusion: don't install league/flysystem 3.14.0 (conflict analysis result)
- Conclusion: don't install league/flysystem 3.15.1 (conflict analysis result)
- Conclusion: don't install league/flysystem 3.29.1 (conflict analysis result)
- You can only install one version of a package, so only one of these can be installed: league/flysystem[1.0.0-alpha1, ..., 1.x-dev, 2.0.0-alpha.1, ..., 2.x-dev, 3.0.0, ..., 3.x-dev].
|
CI
Process completed with exit code 2.
|
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
Loading