Bump Microsoft.AspNetCore.Http from 2.1.22 to 2.2.2 - #2
Closed
dependabot[bot] wants to merge 1 commit into
Closed
Conversation
Bumps [Microsoft.AspNetCore.Http](https://github.com/aspnet/AspNetCore) from 2.1.22 to 2.2.2. - [Release notes](https://github.com/aspnet/AspNetCore/releases) - [Changelog](https://github.com/dotnet/aspnetcore/blob/main/docs/ReleasePlanning.md) - [Commits](dotnet/aspnetcore@v2.1.22...v2.2.2) --- updated-dependencies: - dependency-name: Microsoft.AspNetCore.Http dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
Author
|
Looks like Microsoft.AspNetCore.Http is no longer a dependency, so this is no longer needed. |
dependabot
Bot
deleted the
dependabot/nuget/Microsoft.AspNetCore.Http-2.2.2
branch
March 7, 2022 06:16
marcschier
added a commit
that referenced
this pull request
Jun 15, 2026
… + rename AddOpcUaBindingsPcap → AddPcapBinding Five review comments on Docs/migrate/2.0.x/sessions-subscriptions.md addressed: 1. (line 344) 'These were added in 2.0, no need to discuss migration' — dropped the 'Two additive surface additions for the new WSS reverse-connect path' block and the 'Channel-customization hooks' block. They documented additive 2.0-new surface, not migration guidance from 1.5.378. 2. (line 347) 'Just document the removal of IMessageSocket abstraction, drop the Transports: WSS and HTTPS-JSON' — renamed the section heading from 'Transports: WSS and HTTPS-JSON, IMessageSocket removed' to 'IMessageSocket abstraction removed' and dropped the intro paragraph about the new WSS / HTTPS-JSON transport profiles (also additive, covered by Docs/Profiles.md / WhatsNewIn2.0.md). Kept the IMessageSocket removal table + custom-IMessageSocket migration note as the actual migration content. 3. (line 349) 'Remove this section' — same intent, addressed by #2. 4. (line 434) 'Remove this section since Pcap package is new in 2.0' — dropped the 'Opc.Ua.Bindings.Pcap consumers' block from the Transport-binding-registry section + the 'PcapBindings.Install' line from the DI consumers code snippet. Pcap is new in 2.0 so it has no migration story from 1.5.378. 5. (line 446) 'Rename AddOpcUaBindingsPcap() to AddPcapBinding(). In code, in this PR, no obsoletion required since it is new' — code rename: AddOpcUaBindingsPcap → AddPcapBinding. For symmetry the sister methods follow the same convention: - AddOpcUaBindingsPcap → AddPcapBinding - AddOpcUaBindingsPcapFormatters → AddPcapFormatters - AddOpcUaBindingsPcapReplay → AddPcapReplay All callers updated: PcapServiceCollectionExtensions.cs, PcapBindings.cs (xmldoc), PcapTransportChannelBinding.cs (xmldoc), ChannelCaptureRegistry.cs (xmldoc), IKeyEscrowProvider.cs (xmldoc), NugetREADME.md, Applications/McpServer/Program.cs, Tests/Opc.Ua.Bindings.Pcap.Tests/.../*Tests.cs, Docs/PacketCapture.md. No [Obsolete] shim added per review instruction (the package is new in 2.0 and has no prior consumers to break). Verification: - 'dotnet build Tests/Opc.Ua.Bindings.Pcap.Tests': clean. - 20/20 Pcap DI extension tests pass.
marcschier
added a commit
that referenced
this pull request
Jul 2, 2026
…aling, Warm/Hot client standby Plan items #3 and #4 from plans/28-distributed-ha-remaining.md (items #1/#2 are now issues OPCFoundation#3938/OPCFoundation#3939). #3: RedundantClientSessionFailoverIntegrationTests (Opc.Ua.Sessions.Tests) drives two RedundantClientSession replicas with a controllable leader election against a live ReferenceServer; asserts a follower blocks/throws BadInvalidState, then after a forced handoff the same facade reference keeps serving browse/read over the swapped-in session. Passes net10 + net48. Added a Redundancy.Client project reference. #4a: RedundantServer DNS peer discovery (HA_PEER_DISCOVERY=dns + HA_SERVICE_NAME, self-exclusion + startup retry) + docker-compose.scale.yml so 'docker compose up --scale server=N' self-configures gossip peers. Active/active eventual only; Raft dynamic scaling stays on the Kubernetes StatefulSet path. #4b: RedundantClient --standby <Cold|Warm|Hot> selects the replica-set standby mode; --suite with --replicas>1 runs the browse/read/subscribe workload through the promoted leader facade. RedundantClient AOT-publishes clean. Docs: RedundantClient/RedundantServer READMEs updated; plans/28 moves #3/#4 to Delivered.
marcschier
added a commit
that referenced
this pull request
Jul 31, 2026
Reconcile the PumpX-2000 datasheet work with the address-space compliance changes from OPCFoundation#4117, which reshaped the same sample. Conflict resolutions: - WithIdentification: keep the upstream per-pump signature (builder, pump, pumpNumber) and NodeId-based lookup, and apply the full 21-field datasheet nameplate through it. Unit-specific fields (serial, asset id, component name, location, fabrication number) are now derived from the pump number, so every instance materialised by --pumps N gets a consistent nameplate instead of only the first two. - Program.cs: take upstream. Identification is configured centrally in WithIdentification for every pump, so the per-pump nameplate block in the ConfigureDevicesFor delegate is superseded; the delegate keeps upstream's loop that adds the Diagnostics functional group. - PumpSimulationState.Publish: keep upstream's status code and source timestamp plumbing and publish the datasheet curve values through it. - Supervision booleans: keep upstream's WireBoolean helper (TrueState / FalseState text and history) and drop the alarm's MonitorVariable on the boolean, because the alarm now sources BearingTemperature, which is what its Kelvin trip points describe. - Node-surface baseline: union of both identification lists. - docs/SourceGeneratedNodeManagers.md was consolidated upstream into docs/NodeManagers.md; the datasheet-related snippet fixes were ported there and the old file deleted. Documentation and tests follow the upstream rename of the pump BrowseNames to Pump_1 / Pump_2 (DisplayName "Pump #1" / "Pump #2"). Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: fe608993-f3c9-4779-a6b9-9a9eabfc24ba
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps Microsoft.AspNetCore.Http from 2.1.22 to 2.2.2.
Release notes
Sourced from Microsoft.AspNetCore.Http's releases.
... (truncated)
Commits
522705fMerge pull request #6994 from aspnet/halter73/1531-part22853b45Add RequestAbortedTokenIsUsableAfterCancellation test5d554aeRevert "Wait to dispose RequestAborted CTS (#4447)"f4c5ac7Move Kestrel.Core.Tests to their own test group (#6927)8c06f04Call StopAsync before disposing (#6189) (#6866)a2151cbDo not include prodcon build ID in version metadata829cd72Fix signing for 2.2 site extensions (#6777)c992f0dFix NU1604 error during prodcon builds (#6806)4c1a375Merge branch 'release/2.1' into release/2.2ad31f94Fix failing Razor file comparison tests (#6757)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 mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@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)