Bump Serilog and Serilog.Extensions.Hosting#13
Conversation
Bumps Serilog from 4.2.0 to 4.3.0 Bumps Serilog.Extensions.Hosting from 9.0.0 to 10.0.0 --- updated-dependencies: - dependency-name: Serilog dependency-version: 4.3.0 dependency-type: direct:production update-type: version-update:semver-minor - dependency-name: Serilog.Extensions.Hosting dependency-version: 10.0.0 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
…#4 #5) Subsumes dependabot PRs #1-5 in a single Batch Z-equivalent push. - actions/checkout: v4.2.2 → v6.0.2 - actions/download-artifact: v4.1.8 → v8.0.1 - actions/upload-artifact: v4.4.3 → v7.0.1 - actions/setup-dotnet: v4.1.0 → v5.3.0 - amannn/action-semantic-pull-request: v5.5.3 → v6.1.1 Closes the Node.js 20 deprecation warning that was firing on every job run (force-migration deadline 2026-09-16). All five actions ship Node.js 24-compatible bundles in the new majors. Also configures dependabot's NuGet ecosystem to use the `chore(deps):` commit-message prefix (the github-actions ecosystem already emits `build(deps):` which the pr.yml semantic-PR check already accepts). Without this, NuGet PRs landed with bare "Bump X" titles and failed the title-check before the build job could run — visible in #6 / #7 / #8 / #11 / #13. The five original PRs will be closed once this lands; future dependabot regenerations will use the new prefix and pass the title check.
|
Subsumed by direct main commits d3a3567 (GitHub Actions bumps) and d0e2d4f (NuGet bumps). The original PRs were against the pre-v0.1.0 main and could not be merged without manual rebase; merging directly was faster than rebasing five stale dependabot PRs while a sixth (semantic-PR check) was failing the title gate. Dependabot will pick up new updates on its next weekly cycle and now uses the corrected \ prefix (see .github/dependabot.yml change in d3a3567) so future PRs pass the title check on first try. |
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. You can also ignore all major, minor, or patch releases for a dependency by adding an If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
#13 Manual rebase + apply of the five outstanding NuGet PRs that were sitting against the pre-v0.1.0 main and could no longer be merged straight. All five PRs' version bumps are folded into a single commit so the lock files refresh in lockstep: - Microsoft.Extensions.Logging.Abstractions 10.0.0 → 10.0.8 - Microsoft.Extensions.TimeProvider.Testing 9.7.0 → 10.6.0 - (transitive consistency) Microsoft.Extensions.DependencyInjection / .Abstractions / .Hosting / .Logging all → 10.0.8 so the central pinning doesn't downgrade Logging.Abstractions' transitive deps - Serilog 4.2.0 → 4.3.0 + Serilog.Extensions.Hosting 9.0.0 → 10.0.0 - TestableIO.System.IO.Abstractions + Wrappers + TestingHelpers 22.1.0 → 22.1.1 - OpenTelemetry.Instrumentation.AspNetCore 1.13.0 → 1.15.2 - Microsoft.NET.Test.Sdk 17.14.1 → 18.6.0 - coverlet.collector 6.0.4 → 10.0.1 - Verify.Xunit 28.5.0 → 31.12.5 All 25 packages.lock.json files regenerated via `dotnet restore --force-evaluate`. Suite stays at 623 passing.
1 participant
Updated Serilog from 4.2.0 to 4.3.0.
Release notes
Sourced from Serilog's releases.
4.3.0
What's Changed
LogEvent.AddPropertyIfAbsent(ILogEventPropertyFactory, ...)overload that helps avoid allocations (@vanni-giachin)LogContext.Push()overloads acceptingIEnumerable<ILogEventEnricher>andReadOnlySpan<ILogEventEnricher>(@SimonCropp)New Contributors
Full Changelog: serilog/serilog@v4.2.0...v4.3.0
Commits viewable in compare view.
Updated Serilog.Extensions.Hosting from 9.0.0 to 10.0.0.
Release notes
Sourced from Serilog.Extensions.Hosting's releases.
10.0.0
What's Changed
New Contributors
Full Changelog: serilog/serilog-extensions-hosting@v9.0.0...v10.0.0
Commits viewable in compare view.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)