Urgent, wrong version in nuget feed causing major issues with websites running 1.0.0

[eripe]

In the Optimizely Nuget feed the new released version is on version 1.0.0 and the old one is on 1.1.1. This is causing problem when installing the nuget since we will get the new version instead of the old.

[evest]

Ooh, I can help delete 1.0.0, but I can't get back the old version unless someone sends it to me, or uploads it for approval.

[evest]

New packages are in the feed now. Please try again.

[ErvinsA]

I have reuploaded historical 1.0.0 version and new 1.1.2 version. Please try again and let me know if it helped. Just make sure that you delete nuget local cache first.

[eripe]

It helped and seems to be working. Both 1.1.1 and 1.0.0 is working. Doing a clean deploy each time and so far no problem anymore.

[eripe]

Could also add that 1.1.2 seems to add a breaking change when adding 3 parameters to the DefaultCategoryLoader? Perhaps worth mentioning in the release or have it as a major?

[eripe]

I reopen this issue since we need answer on the last question regarding breaking changes in a minor version update.

[ErvinsA]

Hi @eripe,

In general, constructor parameters are intended for use with dependency injection, which is why we don’t consider this a breaking change. If you need to use it in a scenario where DI is unavailable, you can utilize ServiceLocator.Current.GetInstance().

However, I realized that CategorySettings in DefaultCategoryContentLoader is not actually used in this case. I have removed it and released version 1.1.3 to address this.