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

Bump System.Linq.Dynamic.Core from 1.5.1 to 1.6.0 #112

Closed

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jan 27, 2025

Bumps System.Linq.Dynamic.Core from 1.5.1 to 1.6.0.

Changelog

Sourced from System.Linq.Dynamic.Core's changelog.

v1.6.0 (26 January 2025)

  • #884 - By default the RestrictOrderByToPropertyOrField is now set to true in the ParsingConfig [feature] contributed by StefH
  • #867 - CVE-2024-51417: System.Linq.Dynamic.Core allows remote access to properties on reflection types and static properties/fields [bug]

v1.6.0-preview-03 (25 January 2025)

  • #876 - Update and Fix SecurityTests [test] contributed by mariusz96
  • #882 - ExpressionParser: add 2nd ctor with an extra non-optional parameter [feature] contributed by StefH
  • #883 - Fix the usage of ParsingConfig in some methods in the DynamicQueryableExtensions class [bug] contributed by StefH
  • #881 - ExpressionParser ctor in 1.5.0 not compatible with earlier versions [feature]

v1.6.0-preview-02 (24 January 2025)

  • #874 - Fix calling static properties or fields in non-static class [bug] contributed by StefH
  • #875 - Add option to ParsingConfig to allow the Equals and ToString methods on object [feature] contributed by StefH
  • #879 - Change internal usage from obsolete IDynamicLinkCustomTypeProvider to IDynamicLinqCustomTypeProvider [feature] contributed by StefH
  • #873 - Accessing static property or field in normal class does not work [bug]
  • #878 - ParsingConfig change Type of CustomTypeProvider to IDynamicLinqCustomTypeProvider in Version 1.6.0-preview-01 [feature]

v1.6.0-preview-01 (23 January 2025)

  • #864 - Use ParsingConfig.IsCaseSensitive setting in TextParser and KeywordsHelper [feature] contributed by StefH
  • #865 - Add OrderBy NullPropagation tests [test] contributed by StefH
  • #866 - Refactor KeywordsHelper, TypeFinder and update comments on ParsingConfig [refactor] contributed by StefH
  • #870 - Fix CVE-2024-51417 [bug] contributed by StefH
  • #773 - Parse exceptions with (nested) static classes [bug]
Commits
  • ad66a96 v1.6.0
  • 867d483 By default the RestrictOrderByToPropertyOrField is now set to true in the Par...
  • bd4b8c7 Update README.md [breaking change 1.6.0]
  • 93d5b92 v1.6.0-preview-03
  • cb09b72 Fix the usage of ParsingConfig in some methods in the DynamicQueryableExtensi...
  • bcd8f7b Update and Fix SecurityTests (#876)
  • 1ed7a23 ExpressionParser: add 2nd ctor with an extra non-optional parameter (#882)
  • 233881c v1.6.0-preview-02
  • 1934a14 Add option to ParsingConfig to allow the Equals and ToString methods on objec...
  • fca802e Change internal usage from obsolete IDynamicLinkCustomTypeProvider to IDynami...
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [System.Linq.Dynamic.Core](https://github.com/zzzprojects/System.Linq.Dynamic.Core) from 1.5.1 to 1.6.0.
- [Release notes](https://github.com/zzzprojects/System.Linq.Dynamic.Core/releases)
- [Changelog](https://github.com/zzzprojects/System.Linq.Dynamic.Core/blob/master/CHANGELOG.md)
- [Commits](zzzprojects/System.Linq.Dynamic.Core@v1.5.1...v1.6.0)

---
updated-dependencies:
- dependency-name: System.Linq.Dynamic.Core
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Jan 27, 2025
@CLAassistant
Copy link

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

Copy link
Contributor Author

dependabot bot commented on behalf of github Jan 28, 2025

Superseded by #114.

@dependabot dependabot bot closed this Jan 28, 2025
@dependabot dependabot bot deleted the dependabot/nuget/System.Linq.Dynamic.Core-1.6.0 branch January 28, 2025 19:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant