Magento migrate from version 2.4.5 to 2.4.6

[RonaldNa]

Good morning,

I hope you're all well. I have a question. The Magento I use is currently on version 2.4.5, and we're migrating to 2.4.6. To migrate to 2.4.6, do I need to have all the security patches installed? In other words, do I need version 2.4.5-p12? Or, if I'm using unpatched 2.4.5, can I migrate to 2.4.6?

[AmitVishwakarma · Accepted solution]

Hi @RonaldNa ,

Yes, you can upgrade directly from any 2.4.5 version (patched or unpatched) to 2.4.6.
You do not need to apply 2.4.5-p1, 2.4.5-p2, etc. before upgrading to 2.4.6.

Note:
Security patches in 2.4.5-p1 to p4 are already included in 2.4.6.

Regards,
Amit

[RonaldNa]

Hello @AmitVishwakarma 

Thanks for the clarification

[AmitVishwakarma]

Hi @RonaldNa ,

Glad I could help!
If your issue is resolved, please mark the answer as Accepted Solution so it can help others in the community as well.

Regards,
Amit

[RonaldNa]

Hi @AmitVishwakarma 

I have another question or something else as a suggestion: How good a practice do you think it is to migrate to version 2.4.6, leave the production environment stable with the new version and then progressively add the patches available for that version?

Regards,
Ronald

[AmitVishwakarma]

Hi @RonaldNa ,

Not really. Magento release versions like 2.4.6, 2.4.6-p1, etc. are cumulative.
So once you move to 2.4.6, it’s highly recommended to go straight to the latest patch release like 2.4.6-p5 (or the most recent available).

Why?

1. Security

  - Magento patches are mostly security-related (XSS, RCE, CSRF, etc.).

  - If you're on 2.4.6 (without -p5), your store remains vulnerable to known exploits.

  - Hackers often target stores running outdated patch versions.

2. Stability

  - Patch releases fix critical bugs, performance issues, and compatibility problems.

  - Adobe thoroughly tests patch releases for stability within the same minor version.

  - Skipping patches increases technical debt and debugging difficulty.

3. Progressive patching creates multiple downtime windows

  - Applying patches one at a time means:

  - More deployment windows.

  - More QA cycles.

  - More risks over time.

4. Magento patches are cumulative

  - Example: Upgrading to 2.4.6-p5 gives you everything from 2.4.6, 2.4.6-p1, … p4, all in one go.

  - No need to install patches in order.

Recommended Approach

Instead of:

2.4.6 => stabilize => 2.4.6-p1 => 2.4.6-p2 → ...

Do this:

2.4.5 → directly upgrade to 2.4.6-p5 (or latest patch)

Regards,
Amit

[RonaldNa]

Hello @AmitVishwakarma 

I understand, thanks you for the clarification.

Regards, Ronald