Skip to content

breaking: update logging and dependency-injection abstractions to 10.x - #301

Merged
SamErde merged 6 commits into
mainfrom
dependabot/nuget/src/DLLPickle.Build/multi-e825ecff97
Oct 19, 2026
Merged

SamErde merged 6 commits into
mainfrom
dependabot/nuget/src/DLLPickle.Build/multi-e825ecff97

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Oct 14, 2026 •

Copy link
Copy Markdown
Contributor

Updated Microsoft.Extensions.DependencyInjection.Abstractions from 8.0.2 to 10.0.13.

Release notes

Sourced from Microsoft.Extensions.DependencyInjection.Abstractions's releases.

10.0.0-preview.6.25358.103

You can build .NET 10.0 Preview 6 from the repository by cloning the release tag v10.0.0-preview.6.25358.103 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

10.0.0-preview.5.25277.114

You can build .NET 10.0 Preview 5 from the repository by cloning the release tag v10.0.0-preview.5.25277.114 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

10.0.0-preview.4.25258.110

You can build .NET 10.0 Preview 4 from the repository by cloning the release tag v10.0.0-preview.4.25258.110 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

10.0.0-preview.3.25171.5

You can build .NET 10.0 Preview 3 from the repository by cloning the release tag v10.0.0-preview.3.25171.5 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

10.0.0-preview.2.25163.2

You can build .NET 10.0 Preview 2 from the repository by cloning the release tag v10.0.0-preview.2.25163.2 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

10.0.0-preview.1.25080.5

You can build .NET 10.0 Preview 1 from the repository by cloning the release tag v10.0.0-preview.1.25080.5 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.122

You can build .NET 9.0 from the repository by cloning the release tag v9.0.122 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.121

You can build .NET 9.0 from the repository by cloning the release tag v9.0.121 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.120

You can build .NET 9.0 from the repository by cloning the release tag v9.0.120 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached is a PGP signature for the GitHub generated tarball. You can find the public key at https://dot.net/release-key-2023

9.0.119

You can build .NET 9.0 from the repository by cloning the release tag v9.0.119 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.118

You can build .NET 9.0 from the repository by cloning the release tag v9.0.118 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached is a PGP signature for the GitHub generated tarball. You can find the public key at https://dot.net/release-key-2023

9.0.117

You can build .NET 9.0 from the repository by cloning the release tag v9.0.117 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.116

You can build .NET 9.0 from the repository by cloning the release tag v9.0.116 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.115

You can build .NET 9.0 from the repository by cloning the release tag v9.0.115 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.114

You can build .NET 9.0 from the repository by cloning the release tag v9.0.114 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached is the PGP signature for the GitHub generated tarball. You can find the public key at https://dot.net/release-key-2023

9.0.113

You can build .NET 9.0 from the repository by cloning the release tag v9.0.113 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.112

You can build .NET 9.0 from the repository by cloning the release tag v9.0.112 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.111

You can build .NET 9.0 from the repository by cloning the release tag v9.0.111 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.110

You can build .NET 9.0 from the repository by cloning the release tag v9.0.110 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.109

You can build .NET 9.0 from the repository by cloning the release tag v9.0.109 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.101

You can build .NET 9.0 from the repository by cloning the release tag v9.0.101 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.7

You can build .NET 9.0 from the repository by cloning the release tag v9.0.7 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.6

You can build .NET 9.0 from the repository by cloning the release tag v9.0.6 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.5

You can build .NET 9.0 from the repository by cloning the release tag v9.0.5 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.4

You can build .NET 9.0 from the repository by cloning the release tag v9.0.4 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.3

You can build .NET 9.0 from the repository by cloning the release tag v9.0.3 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.2

You can build .NET 9.0 from the repository by cloning the release tag v9.0.2 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.1

You can build .NET 9.0 from the repository by cloning the release tag v9.0.1 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.0

You can build .NET 9.0 from the repository by cloning the release tag v9.0.0 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.0-rc.2.24473.5

You can build NET 9.0 RC2 from the repository by cloning the release tag v9.0.0-rc.2.24473.5 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.0-rc.1.24431.7

You can build .NET 9.0 RC1 from the repository by cloning the release tag v9.0.0-rc.1.24431.7 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.0-preview.7.24405.7

You can build .NET 9.0 Preview 7 from the repository by cloning the release tag v9.0.0-preview.7.24405.7 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.0-preview.6.24327.7

You can build .NET 9.0 Preview 6 from the repository by cloning the release tag v9.0.0-preview.6.24327.7 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.0-preview.5.24306.7

You can build .NET 9.0 Preview 5 from the repository by cloning the release tag v9.0.0-preview.5.24306.7 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.0-preview.4.24266.19

You can build .NET 9.0 Preview 4 from the repository by cloning the release tag v9.0.0-preview.4.24266.19 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

8.0.132

You can build .NET 8.0 from the repository by cloning the release tag v8.0.132 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

8.0.131

You can build .NET 8.0 from the repository by cloning the release tag v8.0.131 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

8.0.130

You can build .NET 8.0 from the repository by cloning the release tag v8.0.130 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

8.0.129

You can build .NET 8.0 from the repository by cloning the release tag v8.0.129 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

8.0.128

You can build .NET 8.0 from the repository by cloning the release tag v8.0.128 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

8.0.127

You can build .NET 8.0 from the repository by cloning the release tag v8.0.127 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

8.0.126

You can build .NET 8.0 from the repository by cloning the release tag v8.0.126 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

8.0.125

You can build .NET 8.0 from the repository by cloning the release tag v8.0.125 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

8.0.124

You can build .NET 8.0 from the repository by cloning the release tag v8.0.124 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

8.0.123

You can build .NET 8.0 from the repository by cloning the release tag v8.0.123 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

8.0.122

You can build .NET 8.0 from the repository by cloning the release tag v8.0.122 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

8.0.121

You can build .NET 8.0 from the repository by cloning the release tag v8.0.121 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

8.0.120

You can build .NET 8.0 from the repository by cloning the release tag v8.0.120 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

8.0.119

You can build .NET 8.0 from the repository by cloning the release tag v8.0.119 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

8.0.18

You can build .NET 8.0 from the repository by cloning the release tag v8.0.18 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

8.0.17

You can build .NET 8.0 from the repository by cloning the release tag v8.0.17 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

8.0.16

You can build .NET 8.0 from the repository by cloning the release tag v8.0.16 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

8.0.15

You can build .NET 8.0 from the repository by cloning the release tag v8.0.15 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

8.0.14

You can build .NET 8.0 from the repository by cloning the release tag v8.0.14 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

8.0.13

You can build .NET 8.0 from the repository by cloning the release tag v8.0.13 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

8.0.12

You can build .NET 8.0 from the repository by cloning the release tag v8.0.12 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

8.0.11

You can build .NET 8.0 from the repository by cloning the release tag v8.0.11 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

8.0.10

You can build .NET 8.0 from the repository by cloning the release tag v8.0.10 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

8.0.8

You can build .NET 8.0 from the repository by cloning the release tag v8.0.8 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

8.0.7

You can build .NET 8.0 from the repository by cloning the release tag v8.0.7 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

8.0.6

You can build .NET 8.0 from the repository by cloning the release tag v8.0.6 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

8.0.5

You can build .NET 8 from the repository by cloning the release tag v8.0.5 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

Commits viewable in compare view.

Updated Microsoft.Extensions.Logging.Abstractions from 8.0.3 to 10.0.13.

Release notes

Sourced from Microsoft.Extensions.Logging.Abstractions's releases.

10.0.0-preview.6.25358.103

You can build .NET 10.0 Preview 6 from the repository by cloning the release tag v10.0.0-preview.6.25358.103 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

10.0.0-preview.5.25277.114

You can build .NET 10.0 Preview 5 from the repository by cloning the release tag v10.0.0-preview.5.25277.114 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

10.0.0-preview.4.25258.110

You can build .NET 10.0 Preview 4 from the repository by cloning the release tag v10.0.0-preview.4.25258.110 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

10.0.0-preview.3.25171.5

You can build .NET 10.0 Preview 3 from the repository by cloning the release tag v10.0.0-preview.3.25171.5 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

10.0.0-preview.2.25163.2

You can build .NET 10.0 Preview 2 from the repository by cloning the release tag v10.0.0-preview.2.25163.2 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

10.0.0-preview.1.25080.5

You can build .NET 10.0 Preview 1 from the repository by cloning the release tag v10.0.0-preview.1.25080.5 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.122

You can build .NET 9.0 from the repository by cloning the release tag v9.0.122 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.121

You can build .NET 9.0 from the repository by cloning the release tag v9.0.121 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.120

You can build .NET 9.0 from the repository by cloning the release tag v9.0.120 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached is a PGP signature for the GitHub generated tarball. You can find the public key at https://dot.net/release-key-2023

9.0.119

You can build .NET 9.0 from the repository by cloning the release tag v9.0.119 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.118

You can build .NET 9.0 from the repository by cloning the release tag v9.0.118 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached is a PGP signature for the GitHub generated tarball. You can find the public key at https://dot.net/release-key-2023

9.0.117

You can build .NET 9.0 from the repository by cloning the release tag v9.0.117 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.116

You can build .NET 9.0 from the repository by cloning the release tag v9.0.116 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.115

You can build .NET 9.0 from the repository by cloning the release tag v9.0.115 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.114

You can build .NET 9.0 from the repository by cloning the release tag v9.0.114 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached is the PGP signature for the GitHub generated tarball. You can find the public key at https://dot.net/release-key-2023

9.0.113

You can build .NET 9.0 from the repository by cloning the release tag v9.0.113 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.112

You can build .NET 9.0 from the repository by cloning the release tag v9.0.112 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.111

You can build .NET 9.0 from the repository by cloning the release tag v9.0.111 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.110

You can build .NET 9.0 from the repository by cloning the release tag v9.0.110 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.109

You can build .NET 9.0 from the repository by cloning the release tag v9.0.109 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.101

You can build .NET 9.0 from the repository by cloning the release tag v9.0.101 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.7

You can build .NET 9.0 from the repository by cloning the release tag v9.0.7 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.6

You can build .NET 9.0 from the repository by cloning the release tag v9.0.6 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.5

You can build .NET 9.0 from the repository by cloning the release tag v9.0.5 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.4

You can build .NET 9.0 from the repository by cloning the release tag v9.0.4 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.3

You can build .NET 9.0 from the repository by cloning the release tag v9.0.3 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.2

You can build .NET 9.0 from the repository by cloning the release tag v9.0.2 and following the build instructions in the main README.md.

Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.

Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023

9.0.1

You can build .NET ...

Description has been truncated

@dependabot
dependabot Bot requested a review from SamErde as a code owner October 14, 2026 01:38
@dependabot dependabot Bot added .NET Pull requests that update .NET code dependencies Pull requests that update a dependency file labels Oct 14, 2026
@coderabbitai

coderabbitai Bot commented Oct 14, 2026 •

Copy link
Copy Markdown

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration
  • Configuration used: Organization UI
  • Review profile: ASSERTIVE
  • Plan: Advanced
  • Run ID: ac8528bc-f632-4f22-9ac0-b76278895f5d

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@dll-pickle-dependabot-updates
dll-pickle-dependabot-updates Bot marked this pull request as draft October 14, 2026 01:38
@dll-pickle-dependabot-updates

Copy link
Copy Markdown

🔔 Major dependency update — draft for review (not auto-merged, not auto-published)

Per the tracked-dependency release contract (decision 4 / docs/Architecture.md §8.2), a major upstream bump is fully tested but lands as a draft PR with detailed notes. A maintainer promotes it to ready and merges after sign-off; the merge then publishes a major module release (carry the squash commit as breaking:).

Dependencies: Microsoft.Extensions.DependencyInjection.Abstractions, Microsoft.Extensions.Logging.Abstractions

Version change: unknown → 10.0.13

Update type: version-update:semver-major

Package: https://www.nuget.org/packages/Microsoft.Extensions.DependencyInjection.Abstractions — see the package's Release Notes / changelog for breaking changes.

TFM alignment (§8.2 Step 0)

  • 0a — Build gate: restore/build/test green on net8.0 under --locked-mode. See the Checks tab: https://github.com/SamErde/DLLPickle/pull/301/checks
  • 0b — explicit net8.0-consumable asset inspection (including netstandard2.0 and netstandard2.1 where applicable): run tools/Test-DLLPickleTfmAlignment.ps1 against the bumped package(s); the scheduled Upstream-Compatibility candidate flow runs this fail-closed.

Pester / CI: https://github.com/SamErde/DLLPickle/pull/301/checks

Conflict surface / policy impact: a major upstream jump can move the conflict surface. Re-check the Upstream-Compatibility drift gate and re-adjudicate build/dependency-policy.json (classification + evidence + baseline) per §3 if it moved.

Maintainer checklist (complete before marking ready)

  • Re-adjudicate the §3 preload/block classifications for the bumped package(s).
  • Confirm TFM alignment: 0a (Build gate green) and 0b (Test-DLLPickleTfmAlignment.ps1).
  • Refresh the build/dependency-policy.json baseline if the conflict surface moved.
  • Auth-tier real-environment sign-off per §9 (the 2.0.1 precedent) for any bundled-set change.
  • Merge carrying a breaking: prefix so the release publishes a major module version. ⚠️ The default squash subject is Dependabot's deps: commit message, which Get-VersionBump.ps1 maps to a minor bump — edit the squash commit subject to breaking: before confirming the merge, or the release will publish the wrong (minor) version.

@github-actions

github-actions Bot commented Oct 14, 2026 •

Copy link
Copy Markdown
Contributor

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Snapshot Warnings

⚠️: No snapshots were found for the head SHA f28cf79.
Ensure that dependencies are being submitted on PR branches. Re-running this action after a short time may resolve the issue. See the documentation for more information and troubleshooting advice.

OpenSSF Scorecard

PackageVersionScoreDetails
nuget/Microsoft.Extensions.DependencyInjection.Abstractions >= 10, < 11 UnknownUnknown
nuget/Microsoft.Extensions.Logging.Abstractions >= 10, < 11 UnknownUnknown
nuget/System.Diagnostics.DiagnosticSource >= 10, < 11 UnknownUnknown

Scanned Files

  • src/DLLPickle.Build/DLLPickle.csproj

@codacy-production

codacy-production Bot commented Oct 14, 2026 •

Copy link
Copy Markdown
Contributor

Up to standards ✅

🟢 Issues 9 minor

Results:
9 new issues

Category Results
BestPractice 9 minor

View in Codacy

🟢 Metrics 0 complexity · 0 duplication

Metric Results
Complexity ✅ 0 (≤ 100 complexity)
Duplication ✅ 0 (≤ 1 duplication)

View in Codacy

NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.

@SamErde SamErde left a comment

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Deferred: this PR is a draft, which prevents merge. No approval is given.

  • Reviewed head: 1a4289377dade982241e7221feffbc8af47778d6; base: 444dadac4b371f5ea895617d1d5f295102ec1097.
  • Scope: full project/lockfile diff, 2 files, +48/-41. DependencyInjection/Logging abstractions move from 8.x to 10.x with runtime exclusions retained. The lockfile also advances MSAL/IdentityModel/JWT, moves DiagnosticSource to 10.0.13, and introduces cryptography transitives; the runtime compatibility surface is broader than two excluded direct references.
  • Author verified as dependabot[bot] (GitHub user ID 49699333).
  • Checks: Build .NET Packages and dependency-review pass, but required Build gate and Validate upstream compatibility tooling fail. All three OS build jobs and upstream smoke validation encounter the Pester 5.9.0.0 “Assembly with same name is already loaded” error before tests execute. Build evidence, upstream evidence. CodeQL is neutral; CodeRabbit skipped review.
  • Discussion: 4 conversation comments, 0 prior formal reviews, 0 review threads; pagination exhausted. Existing major-update notes call for TFM alignment, preload/block re-adjudication, authenticated compatibility sign-off, and deliberate major-release versioning before promotion/merge.
  • Limitations: static review and hosted logs; no local, authenticated, or release execution. Draft status and failed required verification prevent a safe-to-merge determination.

Merge recommendation: defer until maintainer promotion and completion of the required compatibility checks and major-update sign-off.


AI transparency: Model: gpt-6.1-sol; Effort: high; Tools/skills: GitHub MCP, PR-review workflow; Agents: 1 dedicated repository reviewer plus 1 coordinator.

@dependabot
dependabot Bot force-pushed the dependabot/nuget/src/DLLPickle.Build/multi-e825ecff97 branch from 1a42893 to d1992a0 Compare October 17, 2026 12:24
@dll-pickle-dependabot-updates

Copy link
Copy Markdown

🔔 Major dependency update — draft for review (not auto-merged, not auto-published)

Per the tracked-dependency release contract (decision 4 / docs/Architecture.md §8.2), a major upstream bump is fully tested but lands as a draft PR with detailed notes. A maintainer promotes it to ready and merges after sign-off; the merge then publishes a major module release (carry the squash commit as breaking:).

Dependencies: Microsoft.Extensions.DependencyInjection.Abstractions, Microsoft.Extensions.Logging.Abstractions

Version change: unknown → 10.0.13

Update type: version-update:semver-major

Package: https://www.nuget.org/packages/Microsoft.Extensions.DependencyInjection.Abstractions — see the package's Release Notes / changelog for breaking changes.

TFM alignment (§8.2 Step 0)

  • 0a — Build gate: restore/build/test green on net8.0 under --locked-mode. See the Checks tab: https://github.com/SamErde/DLLPickle/pull/301/checks
  • 0b — explicit net8.0-consumable asset inspection (including netstandard2.0 and netstandard2.1 where applicable): run tools/Test-DLLPickleTfmAlignment.ps1 against the bumped package(s); the scheduled Upstream-Compatibility candidate flow runs this fail-closed.

Pester / CI: https://github.com/SamErde/DLLPickle/pull/301/checks

Conflict surface / policy impact: a major upstream jump can move the conflict surface. Re-check the Upstream-Compatibility drift gate and re-adjudicate build/dependency-policy.json (classification + evidence + baseline) per §3 if it moved.

Maintainer checklist (complete before marking ready)

  • Re-adjudicate the §3 preload/block classifications for the bumped package(s).
  • Confirm TFM alignment: 0a (Build gate green) and 0b (Test-DLLPickleTfmAlignment.ps1).
  • Refresh the build/dependency-policy.json baseline if the conflict surface moved.
  • Auth-tier real-environment sign-off per §9 (the 2.0.1 precedent) for any bundled-set change.
  • Merge carrying a breaking: prefix so the release publishes a major module version. ⚠️ The default squash subject is Dependabot's deps: commit message, which Get-VersionBump.ps1 maps to a minor bump — edit the squash commit subject to breaking: before confirming the merge, or the release will publish the wrong (minor) version.

@dependabot
dependabot Bot force-pushed the dependabot/nuget/src/DLLPickle.Build/multi-e825ecff97 branch from d1992a0 to 1e94a29 Compare October 19, 2026 00:41
@dll-pickle-dependabot-updates

Copy link
Copy Markdown

🔔 Major dependency update — draft for review (not auto-merged, not auto-published)

Per the tracked-dependency release contract (decision 4 / docs/Architecture.md §8.2), a major upstream bump is fully tested but lands as a draft PR with detailed notes. A maintainer promotes it to ready and merges after sign-off; the merge then publishes a major module release (carry the squash commit as breaking:).

Dependencies: Microsoft.Extensions.DependencyInjection.Abstractions, Microsoft.Extensions.Logging.Abstractions

Version change: unknown → 10.0.13

Update type: version-update:semver-major

Package: https://www.nuget.org/packages/Microsoft.Extensions.DependencyInjection.Abstractions — see the package's Release Notes / changelog for breaking changes.

Per-TFM major-update evidence (required before marking ready)

TFM Resolved graph + selected assets Added/removed/changed assemblies Conflict-surface delta Scenario outcomes
net8.0 tfm-alignment.json package composition/size artifacts PowerShell 7.4 Windows/Linux/macOS profile artifacts exact PowerShell 7.4 result artifacts
net9.0 tfm-alignment.json package composition/size artifacts PowerShell 7.5 Windows/Linux/macOS profile artifacts exact PowerShell 7.5 result artifacts
net10.0 tfm-alignment.json package composition/size artifacts PowerShell 7.6 Windows/Linux/macOS profile artifacts exact PowerShell 7.6 result artifacts

The structured JSON reports are attached to the required Build gate and Validate upstream compatibility tooling checks: https://github.com/SamErde/DLLPickle/pull/301/checks. Missing, stale, unaccepted, or drifted profile evidence fails closed; this comment is an index, not a substitute for the artifacts.

Size policy: artifact-size.json must remain within build/artifact-size-baseline.json; a material breach requires explicit review even when the nominal update is minor.

Maintainer checklist (complete before marking ready)

  • Re-adjudicate the §3 preload/block classifications for the bumped package(s).
  • Confirm all three resolved graphs and selected-asset rows in tfm-alignment.json.
  • Review added, removed, and hash-changed assemblies plus per-TFM/full size deltas.
  • Re-adjudicate each profile/platform conflict fingerprint and both import orders.
  • Review every exact-runtime scenario outcome and preserve 🪲 Bug report - Az.Storage and ExchangeOnlineManagement with Get-EXO cmdlets #174 process isolation.
  • Complete the authenticated read-only release gates listed in docs/generated/Compatibility-Evidence.md; do not represent unexecuted probes as passing.
  • Merge carrying a breaking: prefix so the release publishes a major module version. ⚠️ The default squash subject is Dependabot's deps: commit message, which Get-VersionBump.ps1 maps to a minor bump — edit the squash commit subject to breaking: before confirming the merge, or the release will publish the wrong (minor) version.

…Microsoft.Extensions.Logging.Abstractions

Bumps Microsoft.Extensions.DependencyInjection.Abstractions from 8.0.2 to 10.0.13
Bumps Microsoft.Extensions.Logging.Abstractions from 8.0.3 to 10.0.13

---
updated-dependencies:
- dependency-name: Microsoft.Extensions.DependencyInjection.Abstractions
  dependency-version: 10.0.13
  dependency-type: direct:production
  update-type: version-update:semver-major
- dependency-name: Microsoft.Extensions.Logging.Abstractions
  dependency-version: 10.0.13
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/nuget/src/DLLPickle.Build/multi-e825ecff97 branch from 1e94a29 to fe036f0 Compare October 19, 2026 00:44
@dll-pickle-dependabot-updates

Copy link
Copy Markdown

🔔 Major dependency update — draft for review (not auto-merged, not auto-published)

Per the tracked-dependency release contract (decision 4 / docs/Architecture.md §8.2), a major upstream bump is fully tested but lands as a draft PR with detailed notes. A maintainer promotes it to ready and merges after sign-off; the merge then publishes a major module release (carry the squash commit as breaking:).

Dependencies: Microsoft.Extensions.DependencyInjection.Abstractions, Microsoft.Extensions.Logging.Abstractions

Version change: unknown → 10.0.13

Update type: version-update:semver-major

Package: https://www.nuget.org/packages/Microsoft.Extensions.DependencyInjection.Abstractions — see the package's Release Notes / changelog for breaking changes.

Per-TFM major-update evidence (required before marking ready)

TFM Resolved graph + selected assets Added/removed/changed assemblies Conflict-surface delta Scenario outcomes
net8.0 tfm-alignment.json package composition/size artifacts PowerShell 7.4 Windows/Linux/macOS profile artifacts exact PowerShell 7.4 result artifacts
net9.0 tfm-alignment.json package composition/size artifacts PowerShell 7.5 Windows/Linux/macOS profile artifacts exact PowerShell 7.5 result artifacts
net10.0 tfm-alignment.json package composition/size artifacts PowerShell 7.6 Windows/Linux/macOS profile artifacts exact PowerShell 7.6 result artifacts

The structured JSON reports are attached to the required Build gate and Validate upstream compatibility tooling checks: https://github.com/SamErde/DLLPickle/pull/301/checks. Missing, stale, unaccepted, or drifted profile evidence fails closed; this comment is an index, not a substitute for the artifacts.

Size policy: artifact-size.json must remain within build/artifact-size-baseline.json; a material breach requires explicit review even when the nominal update is minor.

Maintainer checklist (complete before marking ready)

  • Re-adjudicate the §3 preload/block classifications for the bumped package(s).
  • Confirm all three resolved graphs and selected-asset rows in tfm-alignment.json.
  • Review added, removed, and hash-changed assemblies plus per-TFM/full size deltas.
  • Re-adjudicate each profile/platform conflict fingerprint and both import orders.
  • Review every exact-runtime scenario outcome and preserve 🪲 Bug report - Az.Storage and ExchangeOnlineManagement with Get-EXO cmdlets #174 process isolation.
  • Complete the authenticated read-only release gates listed in docs/generated/Compatibility-Evidence.md; do not represent unexecuted probes as passing.
  • Merge carrying a breaking: prefix so the release publishes a major module version. ⚠️ The default squash subject is Dependabot's deps: commit message, which Get-VersionBump.ps1 maps to a minor bump — edit the squash commit subject to breaking: before confirming the merge, or the release will publish the wrong (minor) version.

@SamErde
SamErde marked this pull request as ready for review October 19, 2026 00:57
Copilot AI balanced review requested due to automatic review settings October 19, 2026 00:57
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 19, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-19T10:32:17.882493Z f28cf79 New commits
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Changes recommended

Newly introduced runtime dependencies lack policy classifications and violate the existing bundle-validation guard.

2 open issues
What changed in this PR

Updates DLLPickle’s dependency-injection and logging abstractions while refreshing its multi-framework dependency lock file.

Changes:

  • Moves both abstraction references from 8.x to 10.x, resolving to 10.0.13.
  • Refreshes MSAL, IdentityModel, and related transitive dependencies.
File Description
src/​DLLPickle.Build/​packages.lock.json Updates resolved dependencies for .NET 8, 9, and 10.
src/​DLLPickle.Build/​DLLPickle.csproj Raises abstraction package versions while retaining runtime exclusions.

Review effort: Balanced

Comment thread src/DLLPickle.Build/DLLPickle.csproj Resolved
Comment thread src/DLLPickle.Build/packages.lock.json Resolved
@github-actions github-actions Bot added the Build label Oct 19, 2026

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 23b54a72f6

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread build/dependency-policy.json Resolved
Comment thread src/DLLPickle.Build/DLLPickle.csproj Resolved
@SamErde SamErde changed the title deps: Bump Microsoft.Extensions.DependencyInjection.Abstractions and Microsoft.Extensions.Logging.Abstractions breaking: update logging and dependency-injection abstractions to 10.x Oct 19, 2026
@github-actions github-actions Bot added the Tests label Oct 19, 2026
@SamErde

SamErde commented Oct 19, 2026 •

Copy link
Copy Markdown
Owner

Outcome: squash-merged as a78ac4d89e479e4cfce9f68441d2a3cf78efb548; publishing remains blocked pending authenticated evidence.1

Reviewed head: f28cf7922bf860c2eb272bf61ac0ced4ada416dd; base: 1727bf00e36239da57370a259b3ee073de187bf1.

This updates the runtime-excluded logging/dependency-injection abstractions to 10.0.13 while retaining MSAL 4.84.1 and IdentityModel/JWT 8.18.0. DiagnosticSource is directly runtime-excluded, classified, and now tracked by inventory and runtime/ALC snapshots. A regression test prevents any classified assembly from being omitted from tracking.

Nine normalized profile snapshots and their policy baselines were refreshed from collection run 39236885938, whose merge-test commit 8884bd904f2849b8a2ae7c9495ffe282c8e2afcc contains reviewed source 4ce8c689dd2d55f10eb1247c81bad04e1492c423 and the current base. All 72 deterministic scenario outcomes match expectations. DiagnosticSource versions 8.0.0.0, 9.0.0.0, and 10.0.0.0 are host-selected in the Default ALC. After removing only DiagnosticSource observations and derived fingerprints, all nine snapshots exactly match the prior accepted evidence. The generated compatibility register was regenerated; all nine replacement-baseline comparisons and 66 focused tests passed locally.

Final-head CI evidence: all exact-runtime builds, nine-profile upstream compatibility and aggregate gate, locked restore/build/TFM alignment, and dependency review. All four reviewed findings have verified fixes and resolved threads.

Maintainer-authorized sequencing exception: the user explicitly instructed us to merge after the review fixes, refreshed baselines, and passing checks, then complete authenticated validation afterward. Authenticated testing is unexecuted, not approved as passed. Every profile still requires it before release, prohibits writes, and records not-run-no-approved-credentials. The release workflow is byte-identical to main; neither the protected authenticated workflow nor accepted manual evidence exists. A merge-triggered release is therefore expected to stop at its authenticated-evidence gate before versioning, tagging, GitHub release creation, or Gallery publishing.

Merge subject: breaking: update logging and dependency-injection abstractions to 10.x. Merged the pinned reviewed head after confirming all required checks and zero unresolved review threads. No protection bypass or publishing action is authorized.

Post-merge verification: Release and Publish run 39238910686 checked merged candidate a78ac4d89e479e4cfce9f68441d2a3cf78efb548 and stopped at Require Authenticated Compatibility because neither accepted evidence route exists. Version analysis, stamping, tagging, GitHub release creation, and PowerShell Gallery publication were all skipped. Post-merge package validation passed; the other push-triggered checks also completed successfully. Authenticated validation remains outstanding.

Footnotes

  1. Assessed by GPT-6.1 Sol (gpt-6.1-sol), high reasoning effort. Tools: GitHub CLI and PowerShell. Skill: dependabot-merge. Agents: 1. ↩

@github-actions github-actions Bot added the documentation Improvements or additions to documentation label Oct 19, 2026

@SamErde SamErde left a comment

Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved for the explicitly authorized merge-before-authentication sequence at f28cf7922bf860c2eb272bf61ac0ced4ada416dd. See the current assessment and maintainer sequencing instruction.

The logging/DI update remains runtime-excluded, the validated identity graph is retained, DiagnosticSource is excluded/classified/tracked, and all nine refreshed baselines were audited with no unrelated normalized-evidence changes. The 66 focused tests, required CI gates, nine exact-runtime builds, and nine upstream compatibility profiles passed. All review findings are resolved. Authenticated validation is still unexecuted and mandatory before release; the unchanged release guard keeps publishing blocked. Squash subject must start with breaking:.1

Footnotes

  1. Approval assessment by GPT-6.1 Sol (gpt-6.1-sol), high reasoning effort. Tools: GitHub CLI and PowerShell; skill: dependabot-merge; agents: 1. ↩

@SamErde
SamErde merged commit a78ac4d into main Oct 19, 2026
43 checks passed
@SamErde
SamErde deleted the dependabot/nuget/src/DLLPickle.Build/multi-e825ecff97 branch October 19, 2026 10:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Build dependencies Pull requests that update a dependency file documentation Improvements or additions to documentation .NET Pull requests that update .NET code Tests

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants