Mirrors/ArchiSteamFarm
2
0
Fork 0
mirror of https://github.com/JustArchiNET/ArchiSteamFarm synced 2024-09-20 06:22:13 +00:00
Code Issues Projects Releases Packages Wiki Activity
ArchiSteamFarm/Directory.Packages.props

44 lines
2.6 KiB
Text
Raw Normal View History

Manage package versions centrally (#2317) Closes #2316 The issue we're facing right now comes from the fact of desynchronization of packages between different projects. Since I didn't find any way to "fix" the package versions of our plugins to the main ASF project, we'll instead use centralized Directory.packages.props which specifies appropriate versions
2021-05-02 12:51:08 +00:00
<Project>
Remove IndexRange from explicit dependencies Madness implicitly includes it already
2021-08-07 12:08:06 +00:00
<ItemGroup>
<PackageVersion Include="AngleSharp.XPath" Version="1.1.7" />
<PackageVersion Include="ConfigureAwaitChecker.Analyzer" Version="5.0.0" />
<PackageVersion Include="CryptSharpStandard" Version="1.0.0" />
<PackageVersion Include="Humanizer" Version="2.11.10" />
<PackageVersion Include="JetBrains.Annotations" Version="2021.2.0" />
Update dependency Markdig.Signed to v0.26.0
2021-08-27 21:14:32 +00:00
<PackageVersion Include="Markdig.Signed" Version="0.26.0" />
Update dependency Microsoft.NET.Test.Sdk to v16.11.0
2021-08-13 15:55:24 +00:00
<PackageVersion Include="Microsoft.NET.Test.Sdk" Version="16.11.0" />
Remove IndexRange from explicit dependencies Madness implicitly includes it already
2021-08-07 12:08:06 +00:00
<PackageVersion Include="MSTest.TestAdapter" Version="2.2.4" />
<PackageVersion Include="MSTest.TestFramework" Version="2.2.4" />
<PackageVersion Include="Newtonsoft.Json" Version="13.0.1" />
Update dependency Nito.AsyncEx.Coordination to v5.1.2
2021-09-26 02:50:00 +00:00
<PackageVersion Include="Nito.AsyncEx.Coordination" Version="5.1.2" />
Update dependency NLog.Web.AspNetCore to v4.14.0
2021-08-28 22:24:20 +00:00
<PackageVersion Include="NLog.Web.AspNetCore" Version="4.14.0" />
Remove IndexRange from explicit dependencies Madness implicitly includes it already
2021-08-07 12:08:06 +00:00
<PackageVersion Include="SteamKit2" Version="2.4.0-Alpha.3" />
Update swashbuckle-aspnetcore monorepo to v6.2.3
2021-10-16 14:42:55 +00:00
<PackageVersion Include="Swashbuckle.AspNetCore" Version="6.2.3" />
<PackageVersion Include="Swashbuckle.AspNetCore.Annotations" Version="6.2.3" />
<PackageVersion Include="Swashbuckle.AspNetCore.Newtonsoft" Version="6.2.3" />
Remove IndexRange from explicit dependencies Madness implicitly includes it already
2021-08-07 12:08:06 +00:00
<PackageVersion Include="System.Composition" Version="5.0.1" />
<PackageVersion Include="System.Composition.AttributedModel" Version="5.0.1" />
<PackageVersion Include="System.Linq.Async" Version="5.0.0" />
Warn about insecure passwords (#2419) * Add warnings about password security * Warn about weak steam passwords even if they are encrypted * Apply feedback * Apply feedback * Simplify code * Move return criteria up a bit for increased performance * Choose more fitting strings for localization * Extract const value * Fix incorrect null reference warning * Switch prefix operator for postfix one Co-authored-by: Łukasz Domeradzki <JustArchi@JustArchi.net> * Add tests * Disable CA1724 The type name Utilities conflicts in whole or in part with the namespace name 'Microsoft.VisualStudio.TestPlatform.Common.ExtensionFramework.Utilities'. * Tell users why their password is considered weak * Apply feedback * Merge resource comments * Misc. * Use library for password testing and Run testing in background * Clean up * OncSeparate forbidden phrases forfor IPC passwords (once again) * Additionally check encryption key * Add comment about {0} Co-authored-by: Łukasz Domeradzki <JustArchi@JustArchi.net>
2021-10-13 19:44:48 +00:00
<PackageVersion Include="zxcvbn-core" Version="7.0.92" />
Remove IndexRange from explicit dependencies Madness implicitly includes it already
2021-08-07 12:08:06 +00:00
</ItemGroup>
Manage package versions centrally (#2317) Closes #2316 The issue we're facing right now comes from the fact of desynchronization of packages between different projects. Since I didn't find any way to "fix" the package versions of our plugins to the main ASF project, we'll instead use centralized Directory.packages.props which specifies appropriate versions
2021-05-02 12:51:08 +00:00
Include ASF's windows-only parts only in generic and windows builds (#2404) * Include ASF's windows-only parts only in generic and windows builds * Apply Abry's note
2021-08-13 21:07:17 +00:00
<ItemGroup Condition="'$(TargetFramework)' != 'net48' AND ('$(TargetGeneric)' == 'true' OR '$(TargetWindows)' == 'true')">
Remove IndexRange from explicit dependencies Madness implicitly includes it already
2021-08-07 12:08:06 +00:00
<PackageVersion Include="System.IO.FileSystem.AccessControl" Version="5.0.0" />
<PackageVersion Include="System.Security.Cryptography.ProtectedData" Version="5.0.0" />
</ItemGroup>
Manage package versions centrally (#2317) Closes #2316 The issue we're facing right now comes from the fact of desynchronization of packages between different projects. Since I didn't find any way to "fix" the package versions of our plugins to the main ASF project, we'll instead use centralized Directory.packages.props which specifies appropriate versions
2021-05-02 12:51:08 +00:00
Remove IndexRange from explicit dependencies Madness implicitly includes it already
2021-08-07 12:08:06 +00:00
<ItemGroup Condition="'$(TargetFramework)' == 'net48'">
Fix generic-netf update capability For real this time.
2021-09-05 21:05:05 +00:00
<PackageVersion Include="JustArchiNET.Madness" Version="1.3.1" />
Remove IndexRange from explicit dependencies Madness implicitly includes it already
2021-08-07 12:08:06 +00:00
<PackageVersion Include="Microsoft.AspNetCore.Cors" Version="2.2.0" />
<PackageVersion Include="Microsoft.AspNetCore.Diagnostics" Version="2.2.0" />
<PackageVersion Include="Microsoft.AspNetCore.HttpOverrides" Version="2.2.0" />
<PackageVersion Include="Microsoft.AspNetCore.Mvc.Core" Version="2.2.5" />
<PackageVersion Include="Microsoft.AspNetCore.ResponseCaching" Version="2.2.0" />
<PackageVersion Include="Microsoft.AspNetCore.ResponseCompression" Version="2.2.0" />
<PackageVersion Include="Microsoft.AspNetCore.Server.Kestrel" Version="2.2.0" />
<PackageVersion Include="Microsoft.AspNetCore.WebSockets" Version="2.2.1" />
Update dotnet monorepo to v3.1.20
2021-10-12 00:34:36 +00:00
<PackageVersion Include="Microsoft.Extensions.Configuration.Json" Version="3.1.20" />
<PackageVersion Include="Microsoft.Extensions.Logging.Configuration" Version="3.1.20" />
Remove IndexRange from explicit dependencies Madness implicitly includes it already
2021-08-07 12:08:06 +00:00
</ItemGroup>
Manage package versions centrally (#2317) Closes #2316 The issue we're facing right now comes from the fact of desynchronization of packages between different projects. Since I didn't find any way to "fix" the package versions of our plugins to the main ASF project, we'll instead use centralized Directory.packages.props which specifies appropriate versions
2021-05-02 12:51:08 +00:00
</Project>
Reference in a new issue Copy permalink