Add CI check to verify generated plugin compatibility with latest Shopware version

[Ant1gua]

Technical TODO

Add a CI check in the shopware-cli repository that verifies the output of extension create --type plugin remains compatible with the latest supported Shopware version.

Why

Today, the generated plugin scaffold is expected to be valid and usable, but that guarantee can drift over time as Shopware evolves.

What the CI job should do

• Run shopware-cli extension create --type plugin with a minimal set of required inputs.
• Use the generated plugin artifact in a test environment based on the latest supported Shopware version.
• Verify the result by attempting to install the generated plugin in Shopware.
• Fail the pipeline if the generated plugin cannot be installed.

Notes

• using extension validate is not the solution: Create a minimal, valid plugin with extension create #1274 (comment)
• original idea and context: Create a minimal, valid plugin with extension create #1274 (comment)

Acceptance criteria

• A CI workflow exists in shopware/shopware-cli that generates a minimal plugin scaffold using extension create --type plugin.
• The workflow tests that generated scaffold against the latest supported Shopware version.
• The workflow fails when the generated plugin is not installable.
• The workflow is documented clearly enough that future maintainers understand what compatibility guarantee it provides.

[Ant1gua]

[Proposal] Since extension validate would automatically fail, we could also implement an extra validation method for checking a plugins structure and if it is installable. Downside: This would require to update the method if the requirements for valid plugins change. @shopware/product-dx wdyt?

[shyim]

I would say not worth the CI time. we generate soo basic fundemental stuff that will never change 🙈

[MalteJanz]

I would say a small, maybe nightly or weekly, smoke CI test could still be worth it, e.g. just running extension create and all the additive generators + then try installing the plugin in SW + optionally seeing if the storefront returns 200 response. If the commerce core people are responsible for the templates, maybe the CI could even live in the shopware repo, but then a team must feel responsible and monitor / get notifications on that CI 🤷 .

I just vaguely remember that I tried some of the core commands over a year ago to get plugin scaffold quickly and back then it already failed on me (not sure if it was on install or later when trying to visit the storefront).

I agree that the "soo basic fundamental stuff" like the composer file + plugin base class is unlikely to change, but the more specific stuff like admin-module / javascript-plugin / store-api-route / entity and so on might change slightly over time 🤔 .

If we don't have anything in place we could end up in a situation where the templates are broken and nobody notices, unless a user runs into such an error and reports it to us. Which could also be an option but it's a really painful one, especially if someone is just getting started with shopware development and then has to troubleshoot why some generator command produces non working code...

[lasomethingsomething]

Malte Janz (@MalteJanz) Anne (@Ant1gua) Just took a quick look at recent generators activity. This PR is recent and changed some of the generator files shopware/shopware#18663, but prior to that, changes appear sparse.