Andrew Berry

@justafish I was sure there was an existing issue around this, but I don't see one. Perhaps we just talked about this internally at some point? We did something like...

> WARN: Unsupported composer value This looks to be because of our support for multiple major Drupal versions? Or perhaps because we don't have `^10` yet. ``` WARN: Unsupported composer...

I'm calling this a bug because the current implementation is the opposite to what phpcs expects by default, and that's pretty confusing for new users!

I like the idea of a label. Rather than skipping though, I think it should be opt-in - if the label is there, we build the multidev. Something like `build-pantheon-multidev`?

I updated this to also add a one-line change to only run the action at all if composer.lock is modified.

@beto-aveiga is going to review this for https://github.com/Lullabot/drainpipe/issues/318#issuecomment-2117988058 and if there's overlap file a PR against this branch.

I don't think we should drop a version of PHP until it's actually EOL. Otherwise, incoming projects may be unable to adopt Drainpipe without first upgrading PHP, which can be...

One benefit of Renovate is that it also handles yarn, Dockerfiles, docker compose, github actions, and more. > The benefits we found were not having to manage several individual PRs...

Based on our various projects using Renovate, I'm going to close this issue as "won't fix". A few reasons: - Renovate continues to work well across a wide variety of...

> Just having a play locally it's saving around 3 seconds for me vs calling composer install Is that on a regular Drupal core install, or a full client site?...