backward compatibility

[giladTab]

HI

We are trying to upgrade from version 3 to latest and we are facing critical issue :
Migrations not support schema change - only create new tables ( that already exist in V3 )

How can we upgrade safely from V3 to V4 ?

Tnx

[lwwcas]

Hi @giladTab

I want to be transparent with you: 90% of the code base was heavily updated from version 3 to version 4. I sincerely apologize for not being able to maintain backward compatibility between the versions.

Unfortunately, I cannot recommend upgrading directly. It will be necessary to remove version 3 and its tables, and then perform a fresh installation of version 4.

I’m working hard to ensure that this kind of issue doesn’t happen again, but this time it was truly necessary due to significant changes in the codebase, including extensive documentation, bug fixes, structural improvements, and optimizations that made it impossible to maintain version 3.

Please don’t lose confidence in the package due to this issue! I’m committed to making the upgrade process smoother in the future. Thanks for your understanding and support!

Best regards,

[Cronay]

A upgrade guide or heads up in some way would have been nice. When updating the package and running the install command an sql exception is thrown about a field missing. Working backwards from the error about how to properly upgrade the version is a mess. I think a a section in the documentation about how such an upgrade could work would be nice. This way it's an incredible difficult laravel 12 upgrade.

Edit: We migrated away from the package. The old version was quite flexible about being integrated into the project on Prod and local dev environment and the new version isn't unfortunately.