Magento2.Legacy.InstallUpgrade.ObsoleteUpgradeSchemaScript ERROR on --severity=10

[speedupmate]

Magento2.Legacy.InstallUpgrade.ObsoleteUpgradeSchemaScript rule fails on marketplace with ERROR on on --severity=10 application submission.

• Marketplace allows you to submit packages supporting 2.2 where UpgradeSchemaScript was not obsolete yet

• Before Magento 2.3, extension developers were required to write code (PHP scripts) to change the database schema.

• Until marketplace removes 2.2 support this rule is too strict

• Instead of declaring this as ERROR leave it as legacy/deprecated , then extension providers can support broader range of installations within one single package (cost effective) and included setup scripts would be just dead weight to higher versions

[m2-assistant]

Hi @speedupmate. Thank you for your report.
To speed up processing of this issue, make sure that you provided sufficient information.

Add a comment to assign the issue: @magento I am working on this

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[YouCanDoIt12]

@speedupmate did you find any alternative for this issue?

[speedupmate]

@speedupmate did you find any alternative for this issue?

Only option was to ditch old version support to bypass the marketplace review and communicate to customers if older version support is needed they can request this from us directly as I just build a separate package for old version support in parallel with removed files added back. So it's just a marketplace limitation not a real world issue for merchants