Skip to content
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

Update All packages #50

Merged
merged 1 commit into from
Dec 29, 2024
Merged

Update All packages #50

merged 1 commit into from
Dec 29, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 29, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
FluentAssertions (source) 6.12.0 -> 6.12.2 age adoption passing confidence
Moq 4.20.69 -> 4.20.72 age adoption passing confidence
Yarp.ReverseProxy 2.0.1 -> 2.2.0 age adoption passing confidence

Release Notes

fluentassertions/fluentassertions (FluentAssertions)

v6.12.2

Compare Source

What's Changed
Others

Full Changelog: fluentassertions/fluentassertions@6.12.1...6.12.2

v6.12.1

Compare Source

What's Changed
Improvements
  • Improve BeEmpty() and BeNullOrEmpty() performance for IEnumerable<T>, by materializing only the first item - #​2530
Fixes
  • Fixed formatting error when checking nullable DateTimeOffset with BeWithin(...).Before(...) - #​2312
  • BeEquivalentTo will now find and can map subject properties that are implemented through an explicitly-implemented interface - #​2152
  • Fixed that the because and becauseArgs were not passed down the equivalency tree - #​2318
  • BeEquivalentTo can again compare a non-generic IDictionary with a generic one - #​2358
  • Fixed that the FormattingOptions were not respected in inner AssertionScope - #​2329
  • Capitalize true and false in failure messages and make them formattable to a custom BooleanFormatter - #​2390, #​2393
  • Improved the failure message for NotBeOfType when wrapped in an AssertionScope and the subject is null - #​2399
  • Improved the failure message for BeWritable/BeReadable when wrapped in an AssertionScope and the subject is read-only/write-only - #​2399
  • Improved the failure message for ThrowExactly[Async] when wrapped in an AssertionScope and no exception is thrown - #​2398
  • Improved the failure message for [Not]HaveExplicitProperty when wrapped in an AssertionScope and not implementing the interface - #​2403
  • Improved the failure message for [Not]HaveExplicitMethod when wrapped in an AssertionScope and not implementing the interface - #​2403
  • Changed BeEquivalentTo to exclude private protected members from the comparison - #​2417
  • Fixed using BeEquivalentTo on an empty ArraySegment - #​2445, #​2511
  • BeEquivalentTo with a custom comparer can now handle null values - #​2489
  • Ensured that nested calls to AssertionScope(context) create a chained context - #​2607
  • One overload of the AssertionScope constructor would not create an actual scope associated with the thread - #​2607
  • Fixed ThrowWithinAsync not respecting OperationCanceledException - #​2614
  • Fixed using BeEquivalentTo with an IEqualityComparer targeting nullable types - #​2648

Full Changelog: fluentassertions/fluentassertions@6.12.0...6.12.1

moq/moq (Moq)

v4.20.72

Full Changelog

🔨 Other:

  • Question: Sponsorable Attribute in release v4.20.71 #​1513

🔀 Merged:

v4.20.71

Full Changelog

🐛 Fixed bugs:

  • (To delete) #​1497
  • Documentation link gives 404 #​1495
  • mock.Protected().Verify() does not work correctly #​1493
  • Documentation link is broken #​1487
  • Moq library throwing TypeIniatilizationException. #​1459

🔨 Other:

  • Documentation Unavailable Online #​1473
  • Supporting .NET8 #​1462
  • Some source code files is filled with comments like: "Unmerged change from project " #​1451
  • Question: would it make sense to call verify all on a strict mock when the mock gets disposed? #​1440
  • SponsorLink Integration Makes Moq Unuasable due to PII and GDPR Requirements #​1433
  • Default value ILookup<> in loose mode is null #​1391
  • Verifying a protected method when the exact parameter types are not statically known #​1339

🔀 Merged:

v4.20.70

Full Changelog

🔨 Other:

  • a minor changes to improve the readability #​1419
  • Poll on SponsorLink #​1415
  • Change log is not updated since version 4.18.4 #​1406
  • Stop using Moq as a guinea pig to get feedback on and develop SponsorLink #​1396
  • Permanently delete all data from SponsorLink's database that has been collected during builds that included Moq (notably any version 4.20.*) #​1395
  • SponsorLink is now OSS too and no longer bundled #​1384
  • SponsorLink and supporting OSS more broadly #​1374
  • Performance issue with large interfaces #​1350

🔀 Merged:

microsoft/reverse-proxy (Yarp.ReverseProxy)

v2.2.0: 2.2.0

This release supports .NET 6.0 and .NET 8.0. See Getting Started.

The Yarp.ReverseProxy packages are available on NuGet.org.

Breaking changes

  • There are no breaking changes between YARP 2.2.0-preview.1 and 2.2.0.
  • See 2.2.0-preview.1 release notes for the list of breaking changes between YARP 2.1 and 2.2.

Other changes

  • The Forwarded transform now prefers the IPv4 form for dual-mode sockets (#​2509 by @​rkargMsft).
    • E.g. 127.0.0.1 is used instead of ::ffff:127.0.0.1.
    • A similar change was already made for X-Forwarded-For in 2.2.0-preview.1 (#​2400).
  • Added a missing WebSocketCloseReason.ActivityTimeout enum value (#​2571 by @​MihaZupan).
  • Added a TlsFrameHelper.ParsingStatus API (#​2587 by @​wfurt).
    • This information can be used to distinguish between Invalid and Incomplete frames.
  • Removed one async state machine allocation when forwarding a request (#​2586 by @​MihaZupan).
  • Several documentation improvements.

New Contributors

For a full list of changes see here.

v2.1.0: 2.1.0

This release supports .NET 6.0, 7.0, and 8.0. See Getting Started.

The Yarp.ReverseProxy packages are available on NuGet.org.

Breaking changes

  • There are no breaking changes between YARP 2.1.0-preview.1 and 2.1.0.
  • See 2.1.0-preview.1 release notes for the list of breaking changes between YARP 2.0 and 2.1.

Other changes

New Contributors

Full Changelog: microsoft/reverse-proxy@v2.1.0-preview.1...v2.1.0


Configuration

📅 Schedule: Branch creation - "before 5am on Sunday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@Piedone Piedone merged commit eb0abe2 into dev Dec 29, 2024
3 checks passed
@renovate renovate bot deleted the renovate/all-packages branch December 29, 2024 01:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant