Update composer.json

[arturodacostasoler]

Included for laravel/framework and laravel/laravel to be able to try and test this package on Laravel 11.6.0:
|^11.0

[ArlonAntonius]

@arturodacostasoler Thank you for starting the effort on this, let us know if there's anything we can do to help update this package.

[arturodacostasoler]

@arturodacostasoler Thank you for starting the effort on this, let us know if there's anything we can do to help update this package.

Hello and thank you very much for your reply.

It is necessary that the owner of this github package, please update and apply/commit the changes to the composer.json file, to include the two lines that allow using this package in Laravel 11, so that we can test it in that new Laravel version.

Mr. Mike Bronner also proposed making these same changes to the composer.json file in the following link, (also another file is modified in that link so the owner of this package must also evaluate those code line changes):

#1047

I'll be waiting for the composer.json file to be updated including the two lines of "|^11.0" to be able to test this package in Laravel 11, and perhaps also the additional changes proposed by Mr. Mike Bronner.

My best regards.

:)

[OliverWich]

As Laravel 10 is slowly but surely moving towards its EOL, we wanted to update our application.

However, this dependency limitation to only support Laravel 9 and 10 of hyn/tenancy is blocking this transition as it is a very core package to us.

Is there any hope in this getting merged in the near future, or do we need to consider jumping ship to another library?

Support and development on this package seemed to have slowed down a lot in the last years, so this thought was already in the back of our minds.

@ArlonAntonius, what is the maintenance plan for hyn/multi-tenant, is there one or should we consider this as unmaintained/deprecated?
Deprecation would be a shame as this worked for us great for many years, but we need to move forward and cannot afford a core package limiting us with slow updates.

[arturodacostasoler]

As Laravel 10 is slowly but surely moving towards its EOL, we wanted to update our application.

However, this dependency limitation to only support Laravel 9 and 10 of hyn/tenancy is blocking this transition as it is a very core package to us.

Is there any hope in this getting merged in the near future, or do we need to consider jumping ship to another library?

Support and development on this package seemed to have slowed down a lot in the last years, so this thought was already in the back of our minds.

@ArlonAntonius, what is the maintenance plan for hyn/multi-tenant, is there one or should we consider this as unmaintained/deprecated? Deprecation would be a shame as this worked for us great for many years, but we need to move forward and cannot afford a core package limiting us with slow updates.

I'm working with Laravel 11, so I had to use the following known Package as there was no update to our requests to simply update two files to be able to install this package on Laravel 11:

https://github.com/archtechx/tenancy

The archtechx/tenancy Package is interesting and updated on May 22 of 2024.

My best regards and is very sad not to have been able to Test this Package on Laravel 11.

:(

[ArlonAntonius]

Heyhey everybody,

We strive to keep this package at least maintained by updating to later Laravel versions. Updating this package is slightly more difficult than our more recent packages due to it's slightly older approach.

I will try to update it this weekend, but it has many challenges 😅

The organization really recommends you to use https://github.com/tenancy/tenancy as it provides a more robust and modular setup compared to this package and is getting some amazing features in the future 😉

[OliverWich]

The organization really recommends you to use https://github.com/tenancy/tenancy as it provides a more robust and modular setup compared to this package and is getting some amazing features in the future 😉

Is there a migration guide to switch to tenancy/tenancy?
As far as I've seen, there are some pretty big differences and some guide to safely change over without breaking existing deployments (e.g. database structures) when updating would be very much needed for a migration to be feasible.