-
Notifications
You must be signed in to change notification settings - Fork 16
chore(FluentAssertions): Update provided Version to latest free and pin it there #1660
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
base: main
Are you sure you want to change the base?
chore(FluentAssertions): Update provided Version to latest free and pin it there #1660
Conversation
…in it there By pinning the version, the user still has the active choice, to remove the Brackets if he might want to pay for newer versions, but those who may don't want to, but using GitHub actions and dependabot, will not run into licensing problems by accident. This results also in a better user experience
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.
Pull Request Overview
This PR updates the FluentAssertions package version from 6.12.0 to 7.2.0 and pins it to prevent automatic updates that could introduce licensing issues. The change addresses a dependency management concern where users could inadvertently upgrade to paid versions of FluentAssertions through automated dependency updates.
- Updated FluentAssertions version to the latest free (Apache 2.0) version
- Added version pinning using bracket notation to prevent automatic updates
- Improved user experience by preventing accidental licensing issues
|
@jeromelaban what about this? |
|
Not sure what is causing this to fail🤔 https://github.com/unoplatform/uno.templates/actions/runs/16380313603/job/46291634241#step:2:1 |
GitHub Issue (If applicable): closes #1625
PR Type
What kind of change does this PR introduce?
What is the current behavior?
What is the new behavior?
Updated the Version to the latest free (Apache2.0) version
pinning the version of this particular Package
By pinning that version, the user still has the active choice, to remove the Brackets, if he might want to pay for newer versions, but those who may don't want to, but using GitHub actions and dependabot, will not run into licensing problems by accident. This results also in a better user experience
PR Checklist
Please check if your PR fulfills the following requirements:
Other information
Maybe there should be added a note in the documentation thats informing the user about this, but kind of all testing documentation are in contribution section, which makes it not clearly visible for non-contributor users
Maybe that should get added in the templating docs, but those are not on this Repository => can not be included in this PR by that. maybe move the #1606 issue to the appropriate repo, which holds that docs and resolve it there?
Internal Issue (If applicable):