Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Drush Launcher is dead, the default Drush binary path should be the path of Drush binary installed at the project level #272

Open
mxr576 opened this issue Mar 11, 2024 · 1 comment · May be fixed by #273

Comments

@mxr576
Copy link

mxr576 commented Mar 11, 2024

A quote from similar issues about the deprecation of Drush Launcher.

Triggered by the recent presentation on DrupalCon Pittsburg.

Drush 11 got an EOL date: 2023 November. It was also marked as not recommended for Drupal 10. The recommended version is Drush 12.

Drush Launcher is not (officially) compatible with Drush 12 at this moment and it may not be compatible in the future, rather Drush 12 is going to fail nicely when it is called via Drush Launcher: drush-ops/drush-launcher#105

@mxr576
Copy link
Author

mxr576 commented Mar 11, 2024

In theory this approach could be used to dynamically find the project specific bin directory and the drush instance inside

https://getcomposer.org/doc/articles/vendor-binaries.md#finding-the-composer-bin-dir-from-a-binary

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant