-
Notifications
You must be signed in to change notification settings - Fork 26
fix: pin FluentAssertions NuGet version to prevent license issues #698
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
Conversation
…void licensing changes
Thanks a lot for your first contribution! Please check out our contributing guidelines and don't hesitate to ask whatever you need. |
|
Thank you @ankitdhaka07 for the contribution! |
No related issues found. Please ensure there is an open issue related to this change to avoid significant delays or closure. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you
Awesome work, congrats on your first merged pull request and thank you for helping improve everyone's experience! |
Happy to make my first open source contribution :) |
… changes
Issue Number : 697
Summary
Changes
The commit updates the Directory.Packages.props file to pin the FluentAssertions NuGet package version by surrounding the version number with square brackets to prevent unintentional upgrades.
User experience
Checklist
Please leave checklist items unchecked if they do not apply to your change.
Is this a breaking change?
RFC issue number:
Checklist:
Acknowledgment
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.