Bump WolverineFx.RuntimeCompilation from 6.30.0 to 6.36.0

[dependabot]

Updated WolverineFx.RuntimeCompilation from 6.30.0 to 6.36.0.

Release notes

Sourced from WolverineFx.RuntimeCompilation's releases.

6.36.0

Heads up when upgrading

• CircuitBreaker() on a buffered local queue now stops the host from starting with an InvalidListenerConfigurationException (#​4410, #​4412). A buffered local queue can't pause, so the circuit breaker used to be accepted and then silently ignored. Add UseDurableInbox() to the queue, or opts.Policies.UseDurableLocalQueues(), or remove the circuit breaker. Durable local queues and external listeners are unaffected. If you use WolverineFx.AI with DurableQueue = false plus a circuit breaker on the callout queue, this applies to you too.
• In the Event Model, a message handler forwarded from a gRPC RPC now always derives SlicePattern.Command (#​4413).

New

• [SlicePattern] declares the Event Model slice pattern of a message handler whose message has no producer in the model, such as a message from another service or a hosted service (#​4395, #​4413). It only fills the gap: an HTTP route, gRPC RPC, schedule or inbound external system still decides the pattern.
• A Wolverine gRPC client can be injected into a handler (#​4403, #​4409).
• Each retry attempt's trace span links to the failed attempt before it with an ActivityLink (#​4398, #​4405).

Fixes

• Agent assignment: each node now checks its assigned agents against the ones actually running and fixes any mismatch (#​3987, #​4404). The follow-up makes assignment deletes owner-scoped, adds claim-if-absent, and hardens the sweep (#​4407, #​4408).
• Batching: the per-pipeline pending count now counts every batched message, not just listener arrivals (#​4397, #​4406).
• Security: System.Security.Cryptography.Xml is now 10.0.12, clearing a high-severity advisory (#​4401).

Docs

• Local queues and buffered endpoints use System.Threading.Channels, not TPL Dataflow (#​4411).
• Removed the nonexistent EnableNodeAgentSupport() from the exclusive node processing page (#​4414).

6.35.0

Store operation side effects, everywhere

MartenOps covered store / insert / update / delete plus StartStream; anything else meant taking an
IDocumentSession and giving up on the handler being a pure function. All three stores now cover
what their own session API supports.

Op	Marten	Polecat	Fisher
HardDelete, HardDeleteWhere, UndoDeleteWhere	✅	✅	✅
UpdateExpectedVersion	✅	✅	—
UpdateRevision	✅	✅	✅
TryUpdateRevision	✅	—	✅
Patch, PatchWhere	✅	—	✅
QueueSqlCommand	✅	✅	✅
InsertObjects, DeleteObjects	✅	—	—
Append, ArchiveStream	✅	✅	✅
UnArchiveStream, TombstoneStream	—	✅	—

The gaps are deliberate: each set was checked against that store's own session API rather than copied
across, and an op whose Execute could only throw is worse than the absence of one. Polecat's last
row is the reverse case — two operations Marten has no counterpart for.

Every op also implements ITenantedMartenOp / ITenantedPolecatOp / ITenantedFisherOp, so one
extension scopes any of them while preserving the concrete return type:

MartenOps.ArchiveStream(command.OrderId).ForTenant(command.TenantId);
PolecatOps.StoreMany(items).ForTenant(tenantId).With(oneMore);

Thanks to @​erdtsieck for the Marten half, which is where this started.

Event Modeling: a declared model and the code now meet

Three findings from one comparison of a curated Event Model against the application built from it
(#​4385, #​4386, #​4387):

• Slices join on handler type. Slice names are the merge key, and a board names a slice for the
  behaviour (ConfirmAppointment) while a derived source names it for the message type or the route.
  An eleven-slice application assembled as twenty-two with no disagreements — not because the sources
  agreed, but because they never met.
• [Emits(typeof(...))] lets a handler name the events its signature cannot carry. EventsToAppend
  and StartStream erase the element types, so the more idiomatically event-modelled an application
  was, the emptier its derived model got.
• Pattern is left unclaimed for a message handler. A handler cannot tell a Command from an
  Automation, so a declaration wins the role instead of losing to a guess.

⚠️ Behaviour change: a plain message-handler slice no longer reports pattern: "Command" in
event-model output or the ServiceCapabilities snapshot. Pattern is still derived wherever the
code answers the question — HTTP routes, gRPC RPCs, schedules, external systems, and any slice whose
... (truncated)

6.34.0

Seventy commits since 6.33.0. The bulk of it is a sustained performance wave on the durability
and message-execution paths, alongside a new recurring-schedule feature, Native AOT support that
now boots end to end, and a long run of clustering and transport fixes.

New

• Recurring cron-scheduled messages. opts.Schedules registers messages to be published on a
  cron expression, coordinated across the cluster so exactly one node fires each occurrence. (#​4307)
• Azure Service Bus takes a configurable prefix for the system queues it names for itself, plus
  a transport-wide default dead letter queue name. Note the migration hazard called out in the docs
  if you adopt the prefix on an existing deployment. (#​4263, #​4281)
• Amazon SQS takes the same kind of configurable prefix for the queues it names for itself. (#​4292)
• The HTTP transport now answers to plain http:// destinations, not just https://.
  ITransport.AdditionalProtocols is the general mechanism, so any transport with legitimately
  multi-scheme addresses can opt in. (#​4200 / #​4379)
• Broker resource setup honors ResourceMigrationFailureMode. FailFast stays the default and
  keeps resources setup strict; ContinueOnFailures lets a host whose broker topology is
  externally owned log the failures and start. (#​4119 / #​4380)

Performance

The GH-4316 wave, measured on the multi-transport perf rig rather than by inspection. Highlights:

• Recovery poll and handled-cleanup get indexes they can actually use — three partial indexes on
  PostgreSQL and SQL Server, 37ms down to 0.04ms on the measured query. (#​4336)
• Batched outbox stores for Oracle, RavenDB and Cosmos DB — 13.1x on Oracle, 61.4x on
  RavenDB. (#​4369 / #​4370)
• Insert-side coalescing of the last un-batched per-message durability round trips: +24.5%
  throughput and 26% lower publish latency where the application publishes concurrently. (#​4319 / #​4368)
• Fixed-arity batched inserts on PostgreSQL (1.35x) and pooled Envelope bodies above the LOH
  threshold (13.5x at 100KB, with Gen1/Gen2 collections gone). (#​4320, #​4333)
• Batched durability commands are chunked under each provider's parameter ceiling, so a large
  transaction no longer trips SQL Server's 2100-parameter limit. (#​4375 / #​4376)
• Per-message allocation and lookup trims across routing, the send path, the execution pipeline,
  header handling, and metric accumulation. DateTimeOffset.Now is gone from the per-message paths.
  (#​4322, #​4323, #​4324, #​4325, #​4326, #​4328, #​4335)
• Idle polling stops hammering (#​4321); the database queue transports drop their per-poll temp
  tables (#​4334); SQL Server metrics counts come from index metadata instead of three full scans
  (#​4318); Redis Streams gains batched durable arrival, measured at +159% (#​4329).

Two changes measured negative on the rig and were reverted rather than shipped — the Azure Service
Bus prefetch default and the coalescer's Queue shape. Both are recorded so they are not revisited.

Native AOT

A Wolverine application now completes a Native AOT publish and boots through its own bootstrap.
(#​4287, #​4298, #​4301, #​4305). A Native AOT app with any external transport used to die building its
first route — fixed in #​4232 / #​4378. The AOT publish smoke test hard-asserts a full boot.

Clustering, agents and durability

... (truncated)

6.33.0

The headline is a new package. WolverineFx.AI makes a one shot LLM call an ordinary Wolverine message: durable, outbox enrolled, retried by the same rules as everything else, and testable without a model anywhere in sight.

WolverineFx.AI (new package)

An LlmCallout is a message. Return one from a handler next to your storage action and it is enrolled in that handler's outbox, so a callout cannot fire for a transaction that did not commit and cannot be lost to a restart in between. The model's answer comes back as an ordinary cascading message, with an ordinary handler, an ordinary retry policy, and its own place in the correlation chain. (closes #​4227)

• Spend guardrails as middleware on the callout queue. LlmBudget.MaximumPromptCharacters refuses a runaway prompt before your provider is ever called; MaximumTokensPerWindow refuses callouts once the node has burned its allowance. Both dead letter rather than retry, and so does an answer that cannot be parsed into the response type you asked for -- retrying either is the runaway spend the budget exists to stop.
• A scripted IChatClient for testing. StubChatClient exercises a callout's whole round trip with no key, no network and no model.
• Trim and AOT clean, guarded by a Wolverine.AI.AotSmoke project under TrimMode=full that CI runs. (closes #​4230)
• Documentation for tuning it, new in this release: how to control parallelism against your provider, why the answer has its own queue with its own settings, and how to bring your own error handling on both sides.

The package references only the Microsoft.Extensions.AI abstractions, never a vendor SDK. The provider -- Anthropic, OpenAI, Azure, Ollama -- and any middleware over it stay your choice.

Fixes

• A node no longer sweeps up its own in-flight stop as a wedged shard. An event-subscription agent could end up running on two nodes at once while wolverine_nodes credited only one, so nothing in the system could ever stop the extra copy. (closes #​4240)
• Node record descriptions no longer overflow the column and fail the insert. An AssignmentChanged description carries an agent URI, a schema name and a destination node, which on a real cluster overran the description column and failed the whole AgentCommand batch behind it. MySQL was worst hit at VARCHAR(255). (closes #​4246)
• DataAnnotations validation works with ServiceLocationPolicy.NotAllowed -- on HTTP endpoints and, now, on message handlers. Under the Wolverine 6 default this made the validation middleware unusable and threw at bootstrap. (closes #​4238)
• A failed EF Core rollback no longer displaces the exception that caused it. (closes #​4239)
• Wolverine parameter attributes work on gRPC before/after hooks -- [Entity], [All], [Queryable], [WriteAggregate] and the rest. (closes #​3935)
• An application-wide default duplicate status code via opts.DefaultDuplicateStatusCode, and deduplication refusals now advertise their problem document in OpenAPI.
• Concurrent IHost.StopAsync no longer tears the agents down twice.

Upgrade note

6.33.0 requires Weasel 9.30.0, and that raises the GH-4246 fix from "new databases only" to "existing ones too": the schema differ now compares character lengths, so a widened varchar is no longer invisible to it and an existing table is corrected in place by an ALTER TABLE ... MODIFY that keeps its rows.

Worth knowing before you upgrade: that comparison runs in both directions. Width drift that was previously invisible now generates ALTERs, and a model narrower than an existing column will emit a narrowing ALTER that can fail on real data. Sizes that are not character lengths -- a MySQL int(11) display width, a decimal precision, a datetime fsp -- are still ignored.

Dependencies

JasperFx 2.60.0, Marten 9.30.0, Polecat 5.21.1, Fisher 1.0.6, Weasel 9.30.0.

6.32.0

See CHANGELOG.md for the full entries.

New packages

WolverineFx.AmazonS3 and WolverineFx.AzureBlobStorage carry document and saga persistence plus the claim check store that used to ship separately. Registration is explicit per type — Store<T>() and Saga<T>() are separate calls and each refuses the other's type — and saga writes are guarded by conditional requests, surfacing as SagaConcurrencyException so one OnException<ConcurrencyException> policy still covers every store. (#​4160, originally #​4165 by Anne Erdtsieck.)

WolverineFx.ClaimCheck.AmazonS3 is deprecated. The namespace is unchanged, so migration is a package reference swap — but keeping both referenced produces ambiguous-type errors.

Redis document and saga persistence folds into the existing WolverineFx.Redis rather than a new package, with saga concurrency implemented as a Lua compare-and-swap.

Fixes

• A shutting-down node no longer dead-letters work whose handler never ran (#​4213). Core, so every transport.
• Scheduled promotion matches the whole message identity on SQLite, SQL Server, MySQL and Oracle rather than PostgreSQL alone (#​4216) — including a not-yet-due scheduled message being promoted and executed early.
• A redelivered inbox row can be retired when its identity is already handled under EnableInboxPartitioning (#​4216); previously it could not be retired at all.
• A listener whose broker entity was deleted underneath it now heals instead of retrying once a second forever (#​4215).
• Terminal settle failures are classified on the retry block, closing a gap where two of four Azure Service Bus listeners had no classification at all (#​4012).
• Scope priming no longer manufactures a Marten session for every handler that service-locates anything (#​4198). Requires JasperFx 2.58.0 or later.
• A duplicated scheduled identity no longer wedges promotion on a partitioned PostgreSQL inbox (#​4202).
• AddStopConditionIfNull accepts the null identity its signature declares (#​4161).

Diagnostics

• NativeAck and partitioned listeners report ceilings, per-lane depth and duplicate-suppression counts (#​4199). BufferLimit is now null on the modes that never enforced it, with the broker's prefetch window reported as InFlightLimit.
• MaximumBrokerRedeliveries is documented as the delivery count it actually is (#​4216). Behaviour unchanged.

Event model

• A stream-appending handler's return value is reported as a reply rather than an emitted event (#​4204).
• A generic message type's slice reads the way source spells it, which also stops two relays with different payloads colliding on one slice (#​4205).

Also

• Explicit per-provider entity attributes, starting with [FromMarten] and [FromEfCore] (#​4214).
• RabbitMQ documentation for AddResourceSetupOnStartup and AutoProvision (#​4223).

6.31.0

Logical message deduplication

Envelope.Id identifies one delivery. That is the right identity for "the broker handed me this twice" and the wrong one for "the operator clicked Rebuild twice" — those are different deliveries of the same intent, so each carries a different Envelope.Id and every one gets through.

6.31.0 promotes Envelope.DeduplicationId into a first-class logical id, with storage, enforcement, and a retention policy behind it.

opts.Durability.EnableMessageDeduplication = true;   // provisions wolverine_deduplication
opts.Durability.DeduplicationWindow = 24.Hours();    // this IS the guarantee

[Deduplicated]
public static void Handle(RebuildProjection command) { }

It is opt-in throughout — leaving it off means no schema change at all on upgrade. Storage is a separate wolverine_deduplication table rather than a column on the inbox, because under EnableInboxPartitioning the inbox is PARTITION BY LIST (status) and marking an envelope handled moves the row between partitions, which would let one logical id exist as both Incoming and Handled — silently, and only for users who enabled partitioning. Claiming is an INSERT that either succeeds or trips the primary key, never a SELECT-then-INSERT.

Refusals differ per chain type: a message handler discards and acks, HTTP returns 409 with ProblemDetails (configurable to 2xx where a replay is benign), gRPC returns AlreadyExists / InvalidArgument per AIP-193. Storage on PostgreSQL, SQL Server, MySQL and SQLite.

Deriving the id from the message

The publishing side does not have to remember DeliveryOptions.DeduplicationId at every call site. A message type declares its own logical identity once, the way it already declares a topic name with [Topic] or a saga id with [SagaIdentity]:

public record ArchiveInvoice([property: DeduplicationIdentity] string InvoiceNumber, DateOnly AsOf);

[DeduplicationIdentity(nameof(ReceiveShipment.ShipmentId))]   // a contract whose members you cannot decorate
public record ReceiveShipment(Guid ShipmentId, string Warehouse);

// or configured, for composed ids and generated message types
opts.MessageDeduplication.ByMessage<RebuildProjection>(x => $"{x.ProjectionName}|{x.OccurrenceUtc:O}");
opts.MessageDeduplication.ByMemberNamed("IdempotencyKey", "DeduplicationId");
opts.Policies.ForMessagesOfType<CreateOrder>().DeduplicateBy(x => $"{x.Sku}|{x.Quantity}");

These are IEnvelopeRule at the message type level, resolved once when the route is built rather than per message. An explicit DeliveryOptions.DeduplicationId always wins, then configured rules, then the attribute.

Fixes

• Broker startup is bounded by a clock. A host starting against a dead broker took 21m38s to fail — long enough to look like a hang and to blow past any orchestrator's startup probe. (#​4116)
• ListeningAgent sees past its receiver wrappers. ReceiverWithRules — installed by a bare endpoint-level MessageType or TenantId — is unconditionally an ILocalQueue, so a wrapped NativeAck or Inline receiver took the wrong branch and threw on the durability agent's re-entry path. The same blindness meant a terminally faulted receiver reported healthy forever on exactly the endpoints most likely to be non-trivially configured. (#​4188, #​4191)
• A locally-owned shard that stopped with nothing to report is restarted. It was invisible to both recovery paths because each deferred to the other; the status was correct, the assignment was correct, and nothing joined the two. Reached through the console's Rebuild, which completed, acked success, and left the shard dead. (#​4193)
• A NativeAck or Inline listener reports its real queue depth and last receipt instead of 0. (#​4186)
• Event Model derivation stops claiming TriggerLabel, which was beating overlay declarations and minting a SourceDisagreement hotspot per labelled route; and a collection response now reads its element type instead of reporting an assembly-qualified CLR string as a canvas node. (#​4181, #​4182)
• An agent command is never forwarded to the node it is already on. (#​4184)

Dependencies

• JasperFx, JasperFx.Events and the two source generator packages to 2.57.2.

Full changelog: JasperFx/wolverine@V6.30.3...V6.31.0
... (truncated)

6.30.3

Patch release. Requires JasperFx 2.57.1, which ships the code-generation half of two of these fixes.

Several of these failed silently — a host that started clean, passed health checks, and did less than it appeared to. Worth a look if any of the shapes below match your application.

Code generation and service location

• ServiceProviderSource.IsolatedAndScoped is now honored by Wolverine.HTTP (#​4171). An endpoint or middleware asking for an IServiceProvider always received httpContext.RequestServices, whatever you configured. Note the consequence: asking for an IServiceProvider in an endpoint is service location and now registers as such, so under ServiceLocationPolicy.NotAllowed those endpoints will throw where they previously slipped past the policy unnoticed. Message handlers have always behaved this way.

• Scope priming now fires for every chain that service-locates, not only those naming an IServiceProvider (#​4171). If a chain reached service location solely through an opaque scoped/transient registration, its child scope was never primed — so a service-located IMessageContext, IMessageBus, or Marten IDocumentSession was a second, un-enrolled instance rather than the one the handler already owned. Handlers and HTTP endpoints are both covered now.

• Lazy<T> dependencies resolve through their registration (#​4159). An open-generic registration such as TryAddScoped(typeof(Lazy<>), typeof(LazyResolver<>)) was ignored whenever the closed type was itself concrete, and new Lazy<IFoo>() was emitted instead. That compiles and can never work — the first .Value throws MissingMemberException for any service without a public parameterless constructor. Relatedly, AlwaysUseServiceLocationFor(typeof(Lazy<>)) accepted an open generic and then matched nothing; it now matches that generic's closed forms.

Sagas

• ResequencerSaga advances LastSequence when a message is handled, not when it is published (#​4172). A replayed message could let a queue backlog walk past the ordering guard while it was still in flight, reordering the handled sequence.

• An already-sequenced arrival is observable and overridable (#​4175). A message whose order the saga had already passed was handled again in silence. The new shouldHandleAlreadySequenced hook logs a warning by default — behavior is unchanged — and can be overridden to discard, raise a metric, or throw.

Startup

• AutoCreate.None no longer pays for a full schema diff at startup (#​4166).

Full changelog: JasperFx/wolverine@V6.30.2...V6.30.3

6.30.2

This addresses an issue encountered by a JasperFx client hitting a sudden crunch of messages being enqueued into local queues. Not something we expect to be common at all, but now we're better anyway!

What's Changed

• GH-4167: one BatchingProcessor per batched message type, not one per racing caller by @​jeremydmiller in GH-4167: one BatchingProcessor per batched message type, not one per racing caller JasperFx/wolverine#4168
• Adopt JasperFx 2.57.0 (#​4167) by @​jeremydmiller in Adopt JasperFx 2.57.0 (#4167) JasperFx/wolverine#4169

Full Changelog: JasperFx/wolverine@V6.30.1...V6.30.2

6.30.1

There's some CritterWatch related functionality smuggled in here for our forthcoming Event Modeling visualization. Otherwise, this is mostly a ton of fine grained improvements for CI or message broker usage problems detected by dogfooding and some "Mr. AI tool, go try to identify potential problems" action

What's Changed

• Node control endpoints stop publishing OTel spans for agent commands (GH-1670 follow-up) by @​jeremydmiller in Node control endpoints stop publishing OTel spans for agent commands (GH-1670 follow-up) JasperFx/wolverine#4118
• GH-4053: correct the NATS native-ack badge to 6.30 by @​jeremydmiller in GH-4053: correct the NATS native-ack badge to 6.30 JasperFx/wolverine#4120
• GH-4012: document MaximumBrokerRedeliveries and MaximumAckAttempts by @​jeremydmiller in GH-4012: document MaximumBrokerRedeliveries and MaximumAckAttempts JasperFx/wolverine#4122
• GH-3627: document [StreamState] and [StreamEvents] by @​jeremydmiller in GH-3627: document [StreamState] and [StreamEvents] JasperFx/wolverine#4121
• Relay a cancelled job's SIGTERM to the build process by @​jeremydmiller in Relay a cancelled job's SIGTERM to the build process JasperFx/wolverine#4115
• GH-4130: OutboxedSessionFactory resolves the Main message store lazily by @​jeremydmiller in GH-4130: OutboxedSessionFactory resolves the Main message store lazily JasperFx/wolverine#4133
• GH-4132/4128/4129/4127: describe-routing NRE, duplicated EF Core eager check, and two docs scoping fixes by @​jeremydmiller in GH-4132/4128/4129/4127: describe-routing NRE, duplicated EF Core eager check, and two docs scoping fixes JasperFx/wolverine#4134
• GH-4136: a failed message now reaches a terminal tracking state by @​jeremydmiller in GH-4136: a failed message now reaches a terminal tracking state JasperFx/wolverine#4137
• GH-4139: OnException return values no longer collide with the message body variable (CS0136) by @​jeremydmiller in GH-4139: OnException return values no longer collide with the message body variable (CS0136) JasperFx/wolverine#4140
• GH-4125: DoNotAssertOnExceptionsDetected no longer suppresses the tracked-session timeout assertion by @​jeremydmiller in GH-4125: DoNotAssertOnExceptionsDetected no longer suppresses the tracked-session timeout assertion JasperFx/wolverine#4138
• GH-4135: report Received exactly once per receipt by @​jeremydmiller in GH-4135: report Received exactly once per receipt JasperFx/wolverine#4141
• GH-4098: keep the evidence when a job is cancelled at its cap by @​jeremydmiller in GH-4098: keep the evidence when a job is cancelled at its cap JasperFx/wolverine#4142
• GH-4100: guard that no tracked-session budget outlives the CI job cap by @​jeremydmiller in GH-4100: guard that no tracked-session budget outlives the CI job cap JasperFx/wolverine#4143
• GH-4109: report the top three RSS growths, and stop calling them retainers by @​jeremydmiller in GH-4109: report the top three RSS growths, and stop calling them retainers JasperFx/wolverine#4144
• GH-4100: a Pulsar receiving loop no longer dies silently on one exception by @​jeremydmiller in GH-4100: a Pulsar receiving loop no longer dies silently on one exception JasperFx/wolverine#4148
• GH-4149: a Pulsar listener is not "started" until its subscription exists by @​jeremydmiller in GH-4149: a Pulsar listener is not "started" until its subscription exists JasperFx/wolverine#4150
• GH-4152/4147/4146: adopt JasperFx 2.56 provenance and add event-model --url by @​jeremydmiller in GH-4152/4147/4146: adopt JasperFx 2.56 provenance and add event-model --url JasperFx/wolverine#4153
• GH-4145: a service-located session is the handler's session on every store by @​jeremydmiller in GH-4145: a service-located session is the handler's session on every store JasperFx/wolverine#4154
• GH-4151: a Static-mode assembly mismatch fails the deploy, and a message that cannot be executed is dead-lettered by @​jeremydmiller in GH-4151: a Static-mode assembly mismatch fails the deploy, and a message that cannot be executed is dead-lettered JasperFx/wolverine#4155
• Adopt Weasel 9.27.0 by @​jeremydmiller in Adopt Weasel 9.27.0 JasperFx/wolverine#4157
• Bump to 6.30.1 and add the CHANGELOG entries for the release by @​jeremydmiller in Bump to 6.30.1 and add the CHANGELOG entries for the release JasperFx/wolverine#4158

Full Changelog: JasperFx/wolverine@V6.30.0...V6.30.1

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 this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Looks like WolverineFx.RuntimeCompilation is updatable in another way, so this is no longer needed.