You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would probably be a good idea to update the Umbraco version in use on the project. As I don't think there's anything on this project that would benefit from features in Umbraco 11, 12 or 13 at the moment, it's probably most straightfoward to just update to the latest version in the Umbraco 10 LTS branch, currently 10.8.5 which would keep it on the same underlying .net 6 version too.
I did a quick test with updating this via nuget locally, and it seems going to 10.8.5 from the currently used version is quite a smooth upgrade with no obvious issues introduced. However as it does update quite a few other dependent packages and I don't know how the deployment process works in the background, and also would likely go into maintenance mode until someone has logged in and gone through the normal back office upgrade wizard the first time, this might not be a great one to be done as a PR.
The text was updated successfully, but these errors were encountered:
It would probably be a good idea to update the Umbraco version in use on the project. As I don't think there's anything on this project that would benefit from features in Umbraco 11, 12 or 13 at the moment, it's probably most straightfoward to just update to the latest version in the Umbraco 10 LTS branch, currently 10.8.5 which would keep it on the same underlying .net 6 version too.
I did a quick test with updating this via nuget locally, and it seems going to 10.8.5 from the currently used version is quite a smooth upgrade with no obvious issues introduced. However as it does update quite a few other dependent packages and I don't know how the deployment process works in the background, and also would likely go into maintenance mode until someone has logged in and gone through the normal back office upgrade wizard the first time, this might not be a great one to be done as a PR.
The text was updated successfully, but these errors were encountered: