Skip to content

chore(deps): Bump AWSSDK.S3 and 8 others - #9

Merged
jmrobles10 merged 1 commit into
mainfrom
dependabot/nuget/nuget-menores-a913083b20
Nov 9, 2026
Merged

chore(deps): Bump AWSSDK.S3 and 8 others#9
jmrobles10 merged 1 commit into
mainfrom
dependabot/nuget/nuget-menores-a913083b20

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 9, 2026

Copy link
Copy Markdown
Contributor

Pinned AWSSDK.S3 at 4.0.104.11.

Release notes

Sourced from AWSSDK.S3's releases.

No release notes found for this version range.

Commits viewable in compare view.

Pinned JasperFx.Events at 2.101.0.

Release notes

Sourced from JasperFx.Events's releases.

2.101.0

JasperFx 2.101.0 makes the command line work from a Native AOT binary, adds a build warning for a source generator that never reaches the compiler, and fixes assembly scanning on Windows.

Highlights

  • The command line runs from a Native AOT binary (#​1141 / #​1142).
    • What was broken: help, run, describe and every other command failed from a native binary, because commands were found and built through reflection that trimming removes.
    • How it works now: JasperFx.SourceGenerator registers each command, a factory for it and its input, and an [InjectService] injector, as ordinary code the trimmer keeps. JasperFx and JasperFx.Events now ship built with it, and describe no longer throws when referenced-assembly metadata is missing.
    • What you need: reference JasperFx.SourceGenerator in every assembly that contributes commands. The trimming warnings on ApplyJasperFxExtensions / RunJasperFxCommands now say when it is safe to suppress them.
    • How it's kept working: a new aot-cli CI job publishes a CreateSlimBuilder app with Native AOT and runs help, help <command>, an application command, check-env, describe and run from the binary.
    • Docs: Command Line → Native AOT and Running the command line in an AOT binary.
  • JFXEVT1138: a build warning when the events source generator never reaches the compiler (#​1138 / #​1139).
    • When it fires: a JasperFx.Events.SourceGenerator is pinned to a different version than the copy bundled by a store, the SDK keeps the higher copy, and a project target then removes that one.
    • What it says: it names the dropped copy and the runtime version.
    • Opt-out: JasperFxEventsReportLostSourceGenerator=false.
  • Assembly scanning skips runtimes/native folders on Windows too, and skips satellite resource assemblies (#​1143 / #​1145).
    • Windows: the check looked for "/runtimes" with a forward slash, so on Windows every native DLL, such as the coverage collector's covrun64.dll, was tried twice and failed on each host start.
    • Linux: the same full-path match skipped the whole scan for an app installed under a folder whose name started with "native".
    • Satellites: satellite resource assemblies are now skipped as well.
  • CI now runs the test suites on Windows (#​1146).

What's Changed

Full Changelog: JasperFx/jasperfx@v2.100.1...v2.101.0

Commits viewable in compare view.

Updated JasperFx.Events.SourceGenerator from 2.100.1 to 2.101.0.

Release notes

Sourced from JasperFx.Events.SourceGenerator's releases.

2.101.0

JasperFx 2.101.0 makes the command line work from a Native AOT binary, adds a build warning for a source generator that never reaches the compiler, and fixes assembly scanning on Windows.

Highlights

  • The command line runs from a Native AOT binary (#​1141 / #​1142).
    • What was broken: help, run, describe and every other command failed from a native binary, because commands were found and built through reflection that trimming removes.
    • How it works now: JasperFx.SourceGenerator registers each command, a factory for it and its input, and an [InjectService] injector, as ordinary code the trimmer keeps. JasperFx and JasperFx.Events now ship built with it, and describe no longer throws when referenced-assembly metadata is missing.
    • What you need: reference JasperFx.SourceGenerator in every assembly that contributes commands. The trimming warnings on ApplyJasperFxExtensions / RunJasperFxCommands now say when it is safe to suppress them.
    • How it's kept working: a new aot-cli CI job publishes a CreateSlimBuilder app with Native AOT and runs help, help <command>, an application command, check-env, describe and run from the binary.
    • Docs: Command Line → Native AOT and Running the command line in an AOT binary.
  • JFXEVT1138: a build warning when the events source generator never reaches the compiler (#​1138 / #​1139).
    • When it fires: a JasperFx.Events.SourceGenerator is pinned to a different version than the copy bundled by a store, the SDK keeps the higher copy, and a project target then removes that one.
    • What it says: it names the dropped copy and the runtime version.
    • Opt-out: JasperFxEventsReportLostSourceGenerator=false.
  • Assembly scanning skips runtimes/native folders on Windows too, and skips satellite resource assemblies (#​1143 / #​1145).
    • Windows: the check looked for "/runtimes" with a forward slash, so on Windows every native DLL, such as the coverage collector's covrun64.dll, was tried twice and failed on each host start.
    • Linux: the same full-path match skipped the whole scan for an app installed under a folder whose name started with "native".
    • Satellites: satellite resource assemblies are now skipped as well.
  • CI now runs the test suites on Windows (#​1146).

What's Changed

Full Changelog: JasperFx/jasperfx@v2.100.1...v2.101.0

Commits viewable in compare view.

Updated Microsoft.AspNetCore.OpenApi from 10.0.13 to 10.0.14.

Release notes

Sourced from Microsoft.AspNetCore.OpenApi's releases.

No release notes found for this version range.

Commits viewable in compare view.

Pinned QRCoder at 1.8.1.

Release notes

Sourced from QRCoder's releases.

1.8.1

What's Changed

New Contributors

Full Changelog: Shane32/QRCoder@v1.8.0...v1.8.1

1.8.0

What's Changed

New Contributors

Full Changelog: Shane32/QRCoder@v1.7.0...v1.8.0

1.7.0

New Features

Performance Enhancements

Bug Fixes

Documentation Changes

Refactoring and Other Changes

Commits viewable in compare view.

Updated Scalar.AspNetCore from 2.18.6 to 2.19.0.

Release notes

Sourced from Scalar.AspNetCore's releases.

No release notes found for this version range.

Commits viewable in compare view.

Updated WolverineFx.Http from 6.62.0 to 6.63.0.

Release notes

Sourced from WolverineFx.Http's releases.

6.63.0

This is a durability release. Most of its fixes were found by the new out-of-process durability chaos rig (src/Testing/DurabilityChaosRig), which kills, stops, pauses and starves producers and workers, then checks a ledger for lost, duplicated and stuck messages. Dependencies are unchanged from 6.62.0 (JasperFx 2.100.1, Weasel 9.49.0, Marten 9.58.0, Polecat 5.49.0, Fisher 1.28.0). Upgrading is a package bump with no breaking API change. The one schema change is a new index on the MySQL inbox table (GH-5428), applied by the usual message storage migration.

Fixes

  • Envelope ids: default envelope ids no longer collide between processes on one machine. Collisions showed up as inbox duplicate-key errors and silently dropped "duplicate" deliveries (#​5399).
  • Stale nodes: a node that resumes after being ejected as stale does not commit work another node already handled (GH-5423), and Oracle's in-transaction mark-as-handled refuses that work too (GH-5429).
  • Ambiguous commits: a commit that applied but reported an error is no longer dead-lettered, and its cascading messages run (GH-5410).
  • Database queues:
    • scheduled retries are atomic on SQL Server, MySQL, Oracle and SQLite (#​5408), and fenced on the inbox row's owner on every store (GH-5426);
    • the outbox-to-queue move is one transaction on MySQL, SQL Server and SQLite (GH-5438);
    • a durable pop skips envelopes the inbox already holds instead of rolling the whole batch back (GH-5411);
    • a backlog drains without waiting a polling interval per batch (GH-5413).
  • SQL Server: the scheduled-message poll never waits on a lock (GH-5412).
  • MySQL: the expired-handled cleanup no longer locks live inbox rows (GH-5428).
  • SQLite: Balanced mode assigns node numbers and reads health checks as UTC (GH-5430).
  • Multi-tenancy: tenant databases with the same name on one host are told apart by port, so each gets its own durability agent (GH-5435).
  • Dead letters: a dead letter marked replayable mid-move is no longer deleted before it reaches the inbox (GH-5395).
  • Interop: CloudEvents and MassTransit interop keep the inbox id of a durable envelope when they read the message id (#​5396, thanks to @​lahma; #​5398).
  • HTTP: span tags are written before anything can short-circuit the request (GH-5406).
  • Testing: a tracked session no longer completes while a handler's cascading messages are still running (#​5400, thanks to new contributor @​haefele-octoja).

Docs

  • Schema management options for message storage, linked to Weasel and the stateful resource model (#​5437).
  • Waiting on a message the broker fans out to several queues (GH-5416).
  • The durability chaos rig has a README covering its roles, CHAOS_* knobs and containers (GH-5409, GH-5414).

What's Changed

Commits viewable in compare view.

Pinned WolverineFx.Marten at 6.63.0.

Release notes

Sourced from WolverineFx.Marten's releases.

6.63.0

This is a durability release. Most of its fixes were found by the new out-of-process durability chaos rig (src/Testing/DurabilityChaosRig), which kills, stops, pauses and starves producers and workers, then checks a ledger for lost, duplicated and stuck messages. Dependencies are unchanged from 6.62.0 (JasperFx 2.100.1, Weasel 9.49.0, Marten 9.58.0, Polecat 5.49.0, Fisher 1.28.0). Upgrading is a package bump with no breaking API change. The one schema change is a new index on the MySQL inbox table (GH-5428), applied by the usual message storage migration.

Fixes

  • Envelope ids: default envelope ids no longer collide between processes on one machine. Collisions showed up as inbox duplicate-key errors and silently dropped "duplicate" deliveries (#​5399).
  • Stale nodes: a node that resumes after being ejected as stale does not commit work another node already handled (GH-5423), and Oracle's in-transaction mark-as-handled refuses that work too (GH-5429).
  • Ambiguous commits: a commit that applied but reported an error is no longer dead-lettered, and its cascading messages run (GH-5410).
  • Database queues:
    • scheduled retries are atomic on SQL Server, MySQL, Oracle and SQLite (#​5408), and fenced on the inbox row's owner on every store (GH-5426);
    • the outbox-to-queue move is one transaction on MySQL, SQL Server and SQLite (GH-5438);
    • a durable pop skips envelopes the inbox already holds instead of rolling the whole batch back (GH-5411);
    • a backlog drains without waiting a polling interval per batch (GH-5413).
  • SQL Server: the scheduled-message poll never waits on a lock (GH-5412).
  • MySQL: the expired-handled cleanup no longer locks live inbox rows (GH-5428).
  • SQLite: Balanced mode assigns node numbers and reads health checks as UTC (GH-5430).
  • Multi-tenancy: tenant databases with the same name on one host are told apart by port, so each gets its own durability agent (GH-5435).
  • Dead letters: a dead letter marked replayable mid-move is no longer deleted before it reaches the inbox (GH-5395).
  • Interop: CloudEvents and MassTransit interop keep the inbox id of a durable envelope when they read the message id (#​5396, thanks to @​lahma; #​5398).
  • HTTP: span tags are written before anything can short-circuit the request (GH-5406).
  • Testing: a tracked session no longer completes while a handler's cascading messages are still running (#​5400, thanks to new contributor @​haefele-octoja).

Docs

  • Schema management options for message storage, linked to Weasel and the stateful resource model (#​5437).
  • Waiting on a message the broker fans out to several queues (GH-5416).
  • The durability chaos rig has a README covering its roles, CHAOS_* knobs and containers (GH-5409, GH-5414).

What's Changed

Commits viewable in compare view.

Updated WolverineFx.RuntimeCompilation from 6.62.0 to 6.63.0.

Release notes

Sourced from WolverineFx.RuntimeCompilation's releases.

6.63.0

This is a durability release. Most of its fixes were found by the new out-of-process durability chaos rig (src/Testing/DurabilityChaosRig), which kills, stops, pauses and starves producers and workers, then checks a ledger for lost, duplicated and stuck messages. Dependencies are unchanged from 6.62.0 (JasperFx 2.100.1, Weasel 9.49.0, Marten 9.58.0, Polecat 5.49.0, Fisher 1.28.0). Upgrading is a package bump with no breaking API change. The one schema change is a new index on the MySQL inbox table (GH-5428), applied by the usual message storage migration.

Fixes

  • Envelope ids: default envelope ids no longer collide between processes on one machine. Collisions showed up as inbox duplicate-key errors and silently dropped "duplicate" deliveries (#​5399).
  • Stale nodes: a node that resumes after being ejected as stale does not commit work another node already handled (GH-5423), and Oracle's in-transaction mark-as-handled refuses that work too (GH-5429).
  • Ambiguous commits: a commit that applied but reported an error is no longer dead-lettered, and its cascading messages run (GH-5410).
  • Database queues:
    • scheduled retries are atomic on SQL Server, MySQL, Oracle and SQLite (#​5408), and fenced on the inbox row's owner on every store (GH-5426);
    • the outbox-to-queue move is one transaction on MySQL, SQL Server and SQLite (GH-5438);
    • a durable pop skips envelopes the inbox already holds instead of rolling the whole batch back (GH-5411);
    • a backlog drains without waiting a polling interval per batch (GH-5413).
  • SQL Server: the scheduled-message poll never waits on a lock (GH-5412).
  • MySQL: the expired-handled cleanup no longer locks live inbox rows (GH-5428).
  • SQLite: Balanced mode assigns node numbers and reads health checks as UTC (GH-5430).
  • Multi-tenancy: tenant databases with the same name on one host are told apart by port, so each gets its own durability agent (GH-5435).
  • Dead letters: a dead letter marked replayable mid-move is no longer deleted before it reaches the inbox (GH-5395).
  • Interop: CloudEvents and MassTransit interop keep the inbox id of a durable envelope when they read the message id (#​5396, thanks to @​lahma; #​5398).
  • HTTP: span tags are written before anything can short-circuit the request (GH-5406).
  • Testing: a tracked session no longer completes while a handler's cascading messages are still running (#​5400, thanks to new contributor @​haefele-octoja).

Docs

  • Schema management options for message storage, linked to Weasel and the stateful resource model (#​5437).
  • Waiting on a message the broker fans out to several queues (GH-5416).
  • The durability chaos rig has a README covering its roles, CHAOS_* knobs and containers (GH-5409, GH-5414).

What's Changed

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 rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

@dependabot
chore(deps): Bump AWSSDK.S3 and 8 others
f98b50d 
Bumps AWSSDK.S3 from 4.0.104.10 to 4.0.104.11
Bumps JasperFx.Events from 2.100.1 to 2.101.0
Bumps JasperFx.Events.SourceGenerator from 2.100.1 to 2.101.0
Bumps Microsoft.AspNetCore.OpenApi from 10.0.13 to 10.0.14
Bumps QRCoder from 1.6.0 to 1.8.1
Bumps Scalar.AspNetCore from 2.18.6 to 2.19.0
Bumps WolverineFx.Http from 6.62.0 to 6.63.0
Bumps WolverineFx.Marten from 6.62.0 to 6.63.0
Bumps WolverineFx.RuntimeCompilation from 6.62.0 to 6.63.0

---
updated-dependencies:
- dependency-name: AWSSDK.S3
  dependency-version: 4.0.104.11
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: nuget-menores
- dependency-name: JasperFx.Events
  dependency-version: 2.101.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: nuget-menores
- dependency-name: JasperFx.Events.SourceGenerator
  dependency-version: 2.101.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: nuget-menores
- dependency-name: Microsoft.AspNetCore.OpenApi
  dependency-version: 10.0.14
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: nuget-menores
- dependency-name: QRCoder
  dependency-version: 1.8.1
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: nuget-menores
- dependency-name: Scalar.AspNetCore
  dependency-version: 2.19.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: nuget-menores
- dependency-name: WolverineFx.Http
  dependency-version: 6.63.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: nuget-menores
- dependency-name: WolverineFx.Marten
  dependency-version: 6.63.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: nuget-menores
- dependency-name: WolverineFx.RuntimeCompilation
  dependency-version: 6.63.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: nuget-menores
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added .NET Pull requests that update .NET code dependencies Pull requests that update a dependency file labels Nov 9, 2026
@jmrobles10
jmrobles10 merged commit 345bb76 into main Nov 9, 2026
8 checks passed
@dependabot
dependabot Bot deleted the dependabot/nuget/nuget-menores-a913083b20 branch November 9, 2026 05:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@jmrobles10 jmrobles10 jmrobles10 approved these changes

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file .NET Pull requests that update .NET code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@jmrobles10