Repository navigation
Dependencies: SqlClient 7.1.1, Velopack 1.2.161 and two AWS SDK updates - #4963
Merged
Merged
Conversation
Bumps AWSSDK.PI from 4.0.100.14 to 4.0.100.15 Bumps AWSSDK.RDS from 4.0.105.3 to 4.0.106.1 Bumps Microsoft.Data.SqlClient from 7.1.0 to 7.1.1 Bumps Microsoft.Data.SqlClient.Extensions.Azure from 7.1.0 to 7.1.1 Bumps Velopack from 1.2.158 to 1.2.161 --- updated-dependencies: - dependency-name: AWSSDK.PI dependency-version: 4.0.100.15 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-patch-and-minor - dependency-name: AWSSDK.RDS dependency-version: 4.0.106.1 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-patch-and-minor - dependency-name: Microsoft.Data.SqlClient dependency-version: 7.1.1 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-patch-and-minor - dependency-name: Microsoft.Data.SqlClient.Extensions.Azure dependency-version: 7.1.1 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-patch-and-minor - dependency-name: Velopack dependency-version: 1.2.161 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget-patch-and-minor ... Signed-off-by: dependabot[bot] <support@github.com>
…the Storage SqlClient line Dependabot moved Directory.Packages.props and rewrote only some of the packages.lock.json files, so a locked-mode restore failed NU1004 for the rest. This is the result of `dotnet restore PerformanceMonitor.sln --force-evaluate`: the six lock files it still rewrote (Darling.Tests, Darling.Viewer, Lite.Tests, Dashboard.Tests, Installer.Tests, Installer). The two Installer files had Microsoft.Data.SqlClient.Extensions.Azure half-updated at 7.1.0. Dependabot also added a direct Microsoft.Data.SqlClient reference to PerformanceMonitor.Darling.Storage.csproj. Storage already gets SqlClient through PerformanceMonitor.PlanAnalysis, and central package management sets the version, so the line is removed again.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Supersedes #4943.
Why
Dependabot's #4943 moves five packages in
Directory.Packages.propsbut leaves somepackages.lock.jsonfiles on the old versions, so CI's locked-mode restore fails with NU1004 (Darling.Tests, Lite.Tests and Dashboard.Tests were never touched, and the two Installer files were only half updated). This branch is that PR's head, plus a merge of currentdev, plus the missing lock-file regeneration, plus one csproj line taken back out.What each bump brings:
decimalorSqlDecimalparameter whose precision equals its scale threwArgumentException.ClearPoolorClearAllPoolsraced with an open already in progress.IsWow64Process2. The other two items in its notes are npm package updates for Velopack's own repository.What changes
Versions: the five lines in
Directory.Packages.props, exactly as Bump the nuget-patch-and-minor group with 5 updates #4943 has them.Lock files: every
packages.lock.jsonis now consistent with those versions. I randotnet restore PerformanceMonitor.sln --force-evaluateon top of Bump the nuget-patch-and-minor group with 5 updates #4943 and committed everything it rewrote.Lite,deprecated/Dashboard,deprecated/Installer.Coredeprecated/Installer,deprecated/Installer.TestsMicrosoft.Data.SqlClient.Extensions.Azurestill 7.1.0Darling.ViewerDarling.Tests,Lite.Tests,deprecated/Dashboard.TestsUnder
deprecated/only the fivepackages.lock.jsonfiles differ fromdev(git diff --stat origin/dev...HEAD -- deprecated/lists nothing else). Nothing else underdeprecated/changed.Other versions that move because of the bumps (no props line shows them):
Microsoft.Data.SqlClient.Extensions.AbstractionsandMicrosoft.Data.SqlClient.Internal.Logging7.1.0 to 7.1.1 in all nine lock files, andAWSSDK.Core4.0.102.6 to 4.0.102.8 in Darling.Tests.SqlClient credential check from
.github/dependabot.yml: Azure.Identity stays at 1.18.0, Azure.Core at 1.51.1 and Microsoft.Identity.Client at 4.84.2 in all nine lock files, andAzure.Identity.Brokeris absent from all nine. The 7.1.1 notes list no change to credential options. I did not diff SqlClient's source forExcludeBrokerCredentialor the broker's packaging, which is the part of that guidance that has to be read by hand.Two Dashboard lock files carry more than the bumps.
deprecated/Dashboardanddeprecated/Dashboard.Testsstill had project-reference versions of 3.8.0, and listedSystem.Diagnostics.EventLogandSystem.Security.Cryptography.ProtectedData. Regenerating moves the references to 3.9.0 and drops those two entries, which matches the other desktop lock files (Lite, Lite.Tests and Darling.Viewer list neither). The Dashboard copy of that change is already in Bump the nuget-patch-and-minor group with 5 updates #4943; theDashboard.Testscopy comes from the restore.Storage csproj line removed. Bump the nuget-patch-and-minor group with 5 updates #4943 added
<PackageReference Include="Microsoft.Data.SqlClient" />toDarling/PerformanceMonitor.Darling.Storage/PerformanceMonitor.Darling.Storage.csproj. It is taken back out, so that file is identical todev's. Storage already gets SqlClient through its project reference toPerformanceMonitor.PlanAnalysis, which references it directly, and central package management sets the version. Restore and build both pass without the line.Test plan
dotnet restore PerformanceMonitor.sln --force-evaluate: exit 0, rewrote six lock files (Darling.Tests, Darling.Viewer, Lite.Tests, Dashboard.Tests, Installer.Tests, Installer).Lite,Lite.Tests,Installer.Tests,Dashboard.Tests,Darling.Tests,Darling.Viewer, each with--locked-mode): all exit 0, no NU1004.dotnet build PerformanceMonitor.sln -c Debug: Build succeeded, 0 warnings, 0 errors, 19 projects.dev(467cd86, built the same way from a clean export) is also 0 warnings and 0 errors, so the count is the same.build(required): the six locked-mode restores, 0 warnings and 0 errors,Darling.Tests19,892 total with 0 failed, 1,319 skipped (the live PostgreSQL tests, which skip without a PostgreSQL server) and 1 not run,Dashboard.Tests838 with 0 failed,Installer.Tests205 with 0 failed.Lite testsshards 0 to 3: 1,608 + 1,920 + 1,935 + 1,712 = 7,175 tests, 0 failed, 0 skipped.Darling PG testsshards 0 to 2, live PostgreSQL included: 6,518, 6,195 and 7,179 tests, 0 failed, 17 skipped, 1 not run. The requiredDarling PostgreSQL testscheck passes.Darling Linux build,Darling whole-tree guards,check-branchesanddescription-driftpass.Darling.Tests.exeandLite.Tests.exeon a local machine: not run. The CI runs above are the same suites on this exact commit.