- Issue created by @chrisfromredfin
- First commit to issue fork.
working on this issue as my first contrib at DrupalCon 2025 Atlanta. Being mentored by trackleft2
I'm working on this issue at DrupalCon Atlanta 2025. I'll be working on this today with TrackLeft2
- 🇺🇸United States ijf8090
Auto updates was released as a contrib module with Drupal 10 and became part or core with Drupal 11.1 release.
- Merge request !786#3515746 - Deleted help text since package manager ships with a minimum version of 10.2.5 Drupal Core → (Open) created by mshaik
- 🇺🇸United States trackleft2 Tucson, AZ 🇺🇸
I can confirm this is an issue, and found that the minimum Drupal core version that contains packageManager by default is 10.2.5
See https://git.drupalcode.org/project/drupal/-/blob/10.2.4/core/package.jso...
vs
https://git.drupalcode.org/project/drupal/-/blob/10.2.5/core/package.jso...I think we can remove all of the help text that references packageManager
- 🇲🇽Mexico dalin 🇨🇦, 🇲🇽, 🌍
Since Package Manager is a requirement for Project Browser, we should list it as a hard dependency (in the .info.yml file) now that it is included in Drupal Core.
- Merge request !788#3515746 - Removed redundant help message for installing package manager → (Open) created by mshaik
- 🇺🇸United States chrisfromredfin Portland, Maine
Just confirming that Package Manager is not a strict _requirement_ for Project Browser; PB functions without it (though not in as wonderful a way). But it is a soft dependency.
- 🇺🇸United States tim.plunkett Philadelphia
tim.plunkett → made their first commit to this issue’s fork.
- 🇺🇸United States phenaproxima Massachusetts
tim.plunkett → credited phenaproxima → .
- 🇺🇸United States tim.plunkett Philadelphia
Discussed this with @leslieg, @jquijano, @mshaik, and @phenaproxima.
Adam and I suggested that we move AU to require from require-dev, so that it is always in the codebase. Then the message can link to the module install page. But it retains the ability for people to NOT use Package Manager.
Although the suggested changes have been applied, we are facing a blocker with PHPStan. It is reporting failures in files that were not modified, which is both unexpected and impacting our workflow. Interestingly, @tim.plunkett conducted live tests during DrupalCon Atlanta 2025 using his local machine and DrupalPod, where PHPStan executed successfully without any issues. However, these errors appear to be isolated to the pipeline CI environment. Could someone kindly assist us in diagnosing the root cause or suggest potential next steps?