You're managing a Magento 2 site where a critical security update has been released for ottersafe/module-security, bringing it to version 2.0.0. However, some existing modules rely on version 1.5.0 and aren't yet compatible with the latest release.
❓ What approach should you take to implement the security upgrade while awaiting compatibility updates for the other modules?
ℹ️ Are existing requirements blocking a critical module update?
If the module update entails just a small code change, a patch can be a great approach. But if not, or, if there is not a detailed changelog, using a composer inline alias is the quickest and best approach.
---
Connect with Joseph:
LinkedIn: / maxwelljoseph
Twitter: / swiftotter_joe
swiftotter.com
/ swift_otter
/ swiftotterinc
Have you joined the free SwiftOtter Slack community? It's exploding and we don't want you to miss out. Go to swiftotter.com/slack to join for free and get plugged into what might be the best group of collaborating developers around!