A profile without a version causes a fatal error on status report page

Version shouldn't be required for custom profiles so we should be just not be rendering anything for it if it's not there.

Bumping to critical on the basis there must be a lot of versionless custom profiles out there.

kim.pepper → made their first commit to this issue’s fork.

ronbot → changed the visibility of the branch 3511868-a-profile-without to hidden.

ronbot → changed the visibility of the branch 3511868-a-profile-without to active.

kim.pepper → credited atowl → .

kim.pepper → credited ben_a → .

kim.pepper → credited jimmycann → .

kim.pepper → credited lan → .

kim.pepper → credited nterbogt → .

kim.pepper → credited silverham → .

kim.pepper → credited tarawij → .

kim.pepper → credited tyrellblackburn → .

kim.pepper → credited yi_jiang → .

We looked at this at the first-time contributor workshop at DrupalSouth 2025. The following users helped test this manually but could not reproduce:

atowl, lan, yi_jiang, Ronbot, nterbogt, silverham, tarawij, ben_a, cordo1, jimmycann, tyrellblackburn,

We tested by:
1. Deleting the version from the standard.info.yml file (which we installed)
2. Clearing our cache
3. Visiting the Status Report page

Can you please provide more steps to reproduce.

I just got bitten by this after upgrading a D10 site to D11 for the first time ever.

Hello new contributors at DrupalSouth! Here's some guidance for you:
You're right that this can't be reproduced with the Standard profile! The status report page specifically excludes the code that causes the bug when you're on the Standard profile. See the relevant line of code. You can reproduce this with any other profile. Try deleting the version from the Minimal profile instead!

I've updated the issue summary with new instructions.

I have fixed the issue in the MR.
I also took the initiative to change the string used so that it says (minimal) and not (minimal-) if the version is missing. I think it's never actually translated so I won't introduce any further issues with this change.

@vensires Thanks for providing the patch. Since this is a bug report it will need tests in order to be accepted. We do this in order to make certain that the fix isn't accidentally removed in the future.

I have not reviewed or tested the fix yet.

I added a test. It seems a little ridiculous to create a testing profile for this issue, especially since once system's requirements hook is broken up into more manageable and testable pieces then it will be easy to test this with a Unit test. But this is a critical bug and shouldn't wait for that splitting to happen. Maybe there should be a follow-up that's postponed on 📌 [pp-3] Split up and refactor system_requirements() into OOP hooks Active to convert this new Functional test to a Unit test.

1) Drupal\Tests\system\Functional\System\StatusProfileWithoutVersionTest::testStatusPage
Behat\Mink\Exception\ExpectationException: Current response status code is 500, but 200 expected.
/builds/issue/drupal-3511868/vendor/behat/mink/src/WebAssert.php:888
/builds/issue/drupal-3511868/vendor/behat/mink/src/WebAssert.php:145
/builds/issue/drupal-3511868/core/modules/system/tests/src/Functional/System/StatusProfileWithoutVersionTest.php:46

Shows the test coverage

Manually tested following the steps
Deleted version from minimal
Destroyed my local ddev and rebuilt
Visited admin/reports/status and verified the error
Applied the MR and it fixed the issue

LGTM

Committed/pushed to 11.x, thanks!

catch → closed merge request !11523

Automatically closed - issue fixed for 2 weeks with no activity.