lilith
commented
1 month ago 0.8.3 introduced a small breaking change without following semver, but I have re-listed it. There were no vulnerabilities.
On Thu, May 16, 2024 at 2:25 AM Tonći Vatavuk @.***> wrote:
We have just updated all Imageflow dependencies for ToSic.Imageflow.Oqtane in version v1.11.0 https://github.com/2sic/oqtane-imageflow/releases/tag/v1.11.0 and for dnn-imageflow v1.11.0 https://github.com/2sic/dnn-imageflow/releases/tag/v1.11.0. However, we encountered a concern with a transient dependency from Imazen.HybridCache v0.8.3 to Imazen.Common (>= 0.8.3).
When attempting to use Imazen.Common v0.8.3 from NuGet ( https://www.nuget.org/packages/Imazen.Common/0.8.3), we received the following message: "The owner has unlisted this package. This could mean that the package is deprecated, has security vulnerabilities, or shouldn't be used anymore."
Could you please advise on how we should proceed in this case? Should we look for an alternative package, or is there an updated recommendation for handling this dependency?
Thank you for your assistance.
— Reply to this email directly, view it on GitHub https://github.com/imazen/imageflow-dotnet-server/issues/94, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAA2LH44MDG5NDJKAXISGSLZCRUQ7AVCNFSM6AAAAABHZWVACKVHI2DSMVQWIX3LMV43ASLTON2WKOZSGI4TSNZRGMYTGNI . You are receiving this because you are subscribed to this thread.Message ID: @.***>
We have just updated all Imageflow dependencies for ToSic.Imageflow.Oqtane in version v1.11.0 and for dnn-imageflow v1.11.0. However, we encountered a concern with a transient dependency from Imazen.HybridCache v0.8.3 to Imazen.Common (>= 0.8.3).
When attempting to use Imazen.Common v0.8.3 from NuGet (https://www.nuget.org/packages/Imazen.Common/0.8.3), we received the following message: "The owner has unlisted this package. This could mean that the package is deprecated, has security vulnerabilities, or shouldn't be used anymore."
Could you please advise on how we should proceed in this case? Should we look for an alternative package, or is there an updated recommendation for handling this dependency?
Thank you for your assistance.