-
Notifications
You must be signed in to change notification settings - Fork 5
Update nuget #729
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
projectorigin-renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/nuget
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Update nuget #729
Conversation
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
77d56ba to
122403b
Compare
122403b to
75382ea
Compare
75382ea to
436b668
Compare
436b668 to
59bbc55
Compare
59bbc55 to
9ad5381
Compare
9ad5381 to
79686ae
Compare
79686ae to
cd63971
Compare
cd63971 to
3045658
Compare
3045658 to
f5b402f
Compare
f5b402f to
bd06f8b
Compare
bd06f8b to
76bdbb2
Compare
76bdbb2 to
d2c5739
Compare
d2c5739 to
056620d
Compare
|
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.



This PR contains the following updates:
3.32.1->3.33.02.72.0->2.76.09.0.3->9.0.49.0.3->9.0.41.12.0->1.13.11.12.0->1.13.11.12.0->1.13.11.12.0->1.13.11.12.0->1.13.01.12.0->1.13.02.9.17->2.9.329.0.4->9.0.66.0.3->6.1.23.1.4->3.1.5Release Notes
npgsql/npgsql (Npgsql)
v9.0.4v9.0.4 contains several minor bug fixes.
Milestone issues
Full Changelog: npgsql/npgsql@v9.0.3...v9.0.4
open-telemetry/opentelemetry-dotnet (OpenTelemetry)
v1.13.1Release details: 1.13.1
1.13.0, the digital signature (.dll-keyless.sig) andcertificate (
.dll-keyless.pem) files were unintentionally omitted from thepublished NuGet packages.
(
net462,netstandard2.0,netstandard2.1,net8.0,net9.0), ensuringthe integrity of DLL verification using Sigstore cosign.
v1.13.0Release details: 1.13.0
OtlpExportProtocol.Grpcnow set the
TE=trailersHTTP request header to improve interoperability.EventNameis now exported by default asEventNameinstead oflogrecord.event.namewhen specified throughILoggeror the experimentallog bridge API.
StackExchange/StackExchange.Redis (StackExchange.Redis)
v2.9.32Compare Source
What's Changed
Full Changelog: StackExchange/StackExchange.Redis@2.9.25...2.9.32
v2.9.25Compare Source
IMPORTANT: this release changes the distribution of pub/sub channels when using cluster; see 2.9.24 for more details.
What's Changed
This change is a critical fix that fixes a packaging failure in 2.9.24; for the relevant feature changes: see 2.9.24.
Full Changelog: StackExchange/StackExchange.Redis@2.9.24...2.9.25
v2.9.24Compare Source
IMPORTANT: this release changes the distribution of pub/sub channels when using cluster:
(this change is specific to pub/sub with regular
SUBSCRIBEchannels, not "sharded"SSUBSCRIBEchannels)SSUBSCRIBE)SSUBSCRIBEchannels are now randomly distributed to nodes by default, but can optionally use key-like routing by calling.WithKeyRouting()on theRedisChannelvalueThis change represents a safer, "least surprises" default; most people expect their cluster to help distribute load, including pub/sub load, between nodes. This is especially useful when there are few (or even only a single) channel(s) that dominate the pub/sub load, which is surprisingly common. Without this change, all that load would be handled only by a single server, because the channel
my_notificationswould be treated similarly to a key, via hash-slot sharding, and all clients would connect to the node serving that slot - when in reality, any node can be used for subscription, with the server distributing events horizontally to all nodes.If you prefer the routed behaviour: use
.WithKeyRouting()before subscribing.What's Changed
SSUBSCRIBE) routing to random, with newWithKeyRouting()API to opt into routed by @mgravell in #2958New Contributors
Full Changelog: StackExchange/StackExchange.Redis@2.9.17...2.9.24
domaindrivendev/Swashbuckle.AspNetCore (Swashbuckle.AspNetCore)
v9.0.6What's Changed
Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v9.0.5...v9.0.6
v9.0.5What's Changed
Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v9.0.4...v9.0.5
DbUp/dbup-postgresql (dbup-postgresql)
v6.1.2Compare Source
What's Changed
New Contributors
Full Changelog: DbUp/dbup-postgresql@6.0.3...6.1.2
xunit/visualstudio.xunit (xunit.runner.visualstudio)
v3.1.5Compare Source
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Renovate Bot.