search

reactiveui / ReactiveUI

An advanced, composable, functional reactive model-view-viewmodel framework for all .NET platforms that is inspired by functional reactive programming. ReactiveUI allows you to abstract mutable state away from your user interfaces, express the idea around a feature in one readable place and improve the testability of your application.
https://www.reactiveui.net
MIT License
8.11k stars 1.12k forks source link

chore(deps): update dependency microsoft.xaml.behaviors.wpf to v1.1.122 #3834

Closed renovate[bot] closed 5 months ago

renovate[bot] commented 5 months ago

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
Microsoft.Xaml.Behaviors.Wpf (source) 1.1.77 -> 1.1.122 age adoption passing confidence

Release Notes

microsoft/XamlBehaviorsWpf (Microsoft.Xaml.Behaviors.Wpf) ### [`v1.1.122`](https://togithub.com/microsoft/XamlBehaviorsWpf/releases/tag/v1.1.122): Behaviors 1.1.122 ##### What's Changed This release fixes an issue in the XAMLBehaviorsSample.InvokeCommandControl Binding: - Updating the command parameter binding for the ColorCommand property so null isn't being passed as the parameter value by [@​smeddows](https://togithub.com/smeddows) in [https://github.com/microsoft/XamlBehaviorsWpf/pull/145](https://togithub.com/microsoft/XamlBehaviorsWpf/pull/145) **Full Changelog**: https://github.com/microsoft/XamlBehaviorsWpf/compare/v1.1.77...v1.1.122

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

This PR has been generated by Mend Renovate. View repository job log here.

github-actions[bot] commented 4 months ago

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.