Merge branch '4.30-bug-fixes

Hi,

I have now read twice: "Merge branch '4.30-bug-fixes' into develop".
Will NopCommerce create another Relesase for nop4.30 or do you have to install the changes yourself?

Best regards

No, nopCommerce usually don't create another Relesase.
So, it would be same for nop4.30.
You have two options, either pick this branch while start (https://github.com/nopSolutions/nopCommerce/tree/4.30-bug-fixes)
or pick those fixes and apply in your project.

This post may interest you
https://www.nopcommerce.com/en/boards/topic/82279/why-are-changes-made-to-the-released-source-code-without-changing-the-version-number

But, it's still not clear to me which "bug fixes" are immediately released.  The above was done three weeks ago, yet the prior mentioned bug fix merge branch was more recent.  I'm understanding of the fact that they don't change the version due to plugin version mismatch, but I don't see why the team won't publish 'all' the 4.30 bug fixes as a replacement to the 4.30 published release (on their downloads page).

(E.g. If anyone has the setting for VendorSettings ShowVendorOnOrderDetailsPage,  then they will not get the correct results, unless they manually fix their code and rebuild.  Non-devs won't be able to do it themselves.)

Every update on GitHub should contain a new version number (for example 4.30.001).