-
Notifications
You must be signed in to change notification settings - Fork 277
Mark friends-of-behat/mink-extension or behat/mink-extension aboned #370
Comments
Hi @shyim, It seems behat/mink-extension is not maintained anymore (last update: 6 Feb. 2018), friends-of-behat/mink-extension replaces it and supports PHP >= 7 with Symfony 5 compatibility. You should only use friends-of-behat/mink-extension for now. |
Can we mark it on https://packagist.org/packages/behat/mink-extension as aboned? |
You should ping the maintainers for that 😉 |
Packages links to here 🤔 |
I'm not sure if abandoned is correct, but we should make it clear it's probably in bugfix-only mode |
@everzet @pamil @stof @weaverryan Could we get a statement here, please? |
PInging @stof, @everzet, @pamil, @weaverryan: Is this package abandoned? What is the expected replacement to be able to use Behat any more? If it's FOB then let's please deprecate this in the README.md and on Packagist and push a last package with details of the alternatives. Alternatively we can accept all of the changes on FoB and actually support this package and add some more maintainers. |
There is no obligation to continue working on this. But let us know what the plan is, mark it as abandoned and adjust the documentation to no longer point here, if it's dead. Thanks! |
@everzet can you mark the |
The original package is about to be marked as abandoned, see Behat/MinkExtension#370 (comment) Lock file operations: 2 installs, 24 updates, 15 removals - Removing behat/mink-browserkit-driver (v1.3.4) - Removing behat/mink-extension (2.3.1) - Removing behat/mink-goutte-driver (v1.2.1) - Removing fabpot/goutte (v3.3.1) - Removing guzzlehttp/guzzle (6.5.5) - Removing guzzlehttp/promises (1.4.0) - Removing guzzlehttp/psr7 (1.7.0) - Removing psr/http-message (1.0.1) - Removing ralouphie/getallheaders (3.0.3) - Removing symfony/browser-kit (v4.4.17) - Removing symfony/dom-crawler (v4.4.17) - Removing symfony/polyfill-intl-idn (v1.20.0) - Removing symfony/polyfill-php72 (v1.20.0) - Removing symfony/polyfill-php73 (v1.20.0) - Removing symfony/polyfill-php80 (v1.20.0) - Upgrading behat/behat (v3.8.1 => v3.13.0) - Upgrading behat/gherkin (v4.6.2 => v4.9.0) - Upgrading behat/mink (v1.8.1 => v1.10.0) - Upgrading behat/mink-selenium2-driver (v1.4.0 => v1.6.0) - Upgrading behat/transliterator (v1.3.0 => v1.5.0) - Locking friends-of-behat/mink-extension (v2.7.2) - Upgrading instaclick/php-webdriver (1.4.7 => 1.4.16) - Upgrading psr/container (1.0.0 => 2.0.2) - Upgrading symfony/config (v4.4.17 => v6.3.0) - Upgrading symfony/console (v5.2.0 => v6.3.0) - Upgrading symfony/css-selector (v5.2.0 => v6.3.0) - Upgrading symfony/dependency-injection (v4.4.17 => v6.3.0) - Upgrading symfony/deprecation-contracts (v2.2.0 => v3.3.0) - Upgrading symfony/event-dispatcher (v5.2.0 => v6.3.0) - Upgrading symfony/event-dispatcher-contracts (v2.2.0 => v3.3.0) - Upgrading symfony/filesystem (v5.2.0 => v6.3.0) - Upgrading symfony/polyfill-ctype (v1.20.0 => v1.27.0) - Upgrading symfony/polyfill-intl-grapheme (v1.20.0 => v1.27.0) - Upgrading symfony/polyfill-intl-normalizer (v1.20.0 => v1.27.0) - Upgrading symfony/polyfill-mbstring (v1.20.0 => v1.27.0) - Upgrading symfony/service-contracts (v2.2.0 => v3.3.0) - Upgrading symfony/string (v5.2.0 => v6.3.0) - Upgrading symfony/translation (v4.4.17 => v6.3.0) - Upgrading symfony/translation-contracts (v2.3.0 => v3.3.0) - Locking symfony/var-exporter (v6.3.0) - Upgrading symfony/yaml (v5.2.0 => v6.3.0)
The original package is about to be marked as abandoned, see Behat/MinkExtension#370 (comment) Lock file operations: 2 installs, 26 updates, 13 removals - Removing behat/mink-browserkit-driver (v1.3.4) - Removing behat/mink-extension (2.3.1) - Removing behat/mink-goutte-driver (v1.2.1) - Removing fabpot/goutte (v3.3.1) - Removing guzzlehttp/guzzle (6.5.5) - Removing guzzlehttp/promises (1.4.0) - Removing guzzlehttp/psr7 (1.7.0) - Removing psr/http-message (1.0.1) - Removing ralouphie/getallheaders (3.0.3) - Removing symfony/browser-kit (v4.4.17) - Removing symfony/dom-crawler (v4.4.17) - Removing symfony/polyfill-intl-idn (v1.20.0) - Removing symfony/polyfill-php72 (v1.20.0) - Upgrading behat/behat (v3.8.1 => v3.13.0) - Upgrading behat/gherkin (v4.6.2 => v4.9.0) - Upgrading behat/mink (v1.8.1 => v1.10.0) - Upgrading behat/mink-selenium2-driver (v1.4.0 => v1.6.0) - Upgrading behat/transliterator (v1.3.0 => v1.5.0) - Locking friends-of-behat/mink-extension (v2.7.2) - Upgrading instaclick/php-webdriver (1.4.7 => 1.4.16) - Upgrading psr/container (1.0.0 => 1.1.2) - Upgrading symfony/config (v4.4.17 => v5.4.21) - Upgrading symfony/console (v5.2.0 => v5.4.24) - Upgrading symfony/css-selector (v5.2.0 => v5.4.21) - Upgrading symfony/dependency-injection (v4.4.17 => v5.4.24) - Upgrading symfony/deprecation-contracts (v2.2.0 => v2.5.2) - Upgrading symfony/event-dispatcher (v5.2.0 => v5.4.22) - Upgrading symfony/event-dispatcher-contracts (v2.2.0 => v2.5.2) - Upgrading symfony/filesystem (v5.2.0 => v5.4.23) - Upgrading symfony/polyfill-ctype (v1.20.0 => v1.27.0) - Upgrading symfony/polyfill-intl-grapheme (v1.20.0 => v1.27.0) - Upgrading symfony/polyfill-intl-normalizer (v1.20.0 => v1.27.0) - Upgrading symfony/polyfill-mbstring (v1.20.0 => v1.27.0) - Upgrading symfony/polyfill-php73 (v1.20.0 => v1.27.0) - Upgrading symfony/polyfill-php80 (v1.20.0 => v1.27.0) - Locking symfony/polyfill-php81 (v1.27.0) - Upgrading symfony/service-contracts (v2.2.0 => v2.5.2) - Upgrading symfony/string (v5.2.0 => v5.4.22) - Upgrading symfony/translation (v4.4.17 => v5.4.24) - Upgrading symfony/translation-contracts (v2.3.0 => v2.5.2) - Upgrading symfony/yaml (v5.2.0 => v5.4.23)
Hey,
it seems so that there are 2 packages. I get lot issues like
Warning: Ambiguous class resolution, "Behat\MinkExtension\Context\MinkAwareContext" was found 2x: in "/home/shyim/Code/shopware/vendor/behat/mink-extension/src/Behat/MinkExtension/Context/MinkAwareContext.php" and "/home/shyim/Code/shopware/vendor/friends-of-behat/mink-extension/src/Behat/MinkExtension/Context/MinkAwareContext.php", the first will be used.
Is this packaged renamed? 🤔
The text was updated successfully, but these errors were encountered: