Moshe Weitzman
Moshe Weitzman
Since maintainers often commit their project's add-ons to the repo, its problematic to have the add-on's version vary by Drupal core version. I think we should explore that backward compat...
I looked at at backward compat and I dont really feel like writing it. If anyone submits a PR, I'd be thankful. until then, we probably have to go with...
I created a 1.x branch and then merged this PR into main. 1.x will get minimal maintenance. Also, I also released 2.0.0-rc1. That can be installed via `ddev add-on get...
Also note that I used the new release with my `keycdn` contrib project and my WebDriverTestBase test is passing along with Drupal 10.5. Is the backward compat issue limited to...
It looks like `ddev add-on get` is fetching 2.0.0-rc1 by default even though its marked as pre-release. Not my intention, but its OK.
I guess we could put it in this repo (or a gist) and then folks run it with `php -r`. See [Composer download](https://getcomposer.org/download/) for an example of that.
Or a bash script if host side PHP is a barrier
My preference is to check in .ddev. When folks need to switch drupal versions, they can uncomment a line in a [config.local.yml](https://ddev.readthedocs.io/en/stable/users/configuration/config/#environmental-overrides), ddev restart, and ddev poser. Or skip the...
Seems like you have an odd version of consolidation/robo in your vendor. Maybe try to update that.