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 Castle.Core from 4.4.0 to 5.1.0 #162

Closed
wants to merge 1 commit into from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Aug 2, 2022

Bumps Castle.Core from 4.4.0 to 5.1.0.

Release notes

Sourced from Castle.Core's releases.

5.1.0

Enhancements

  • Support for covariant method returns (@​stakx, #619)
  • Performance improvement with proxy type generation for class proxies (without target). Abstract class methods now reuse a predefined invocation type (like methods of interface proxies without target; see explanation below at version 5.0.0 enhancements) (@​stakx, #626)

Bugfixes

  • DynamicProxy emits invalid metadata for redeclared event (@​stakx, #590)
  • Proxies using records with a base class broken using .NET 6 compiler (@​ajcvickers, #601)
  • MissingMethodException when proxying interfaces containing sealed methods (@​stakx, #621)

5.0.0

Enhancements

  • .NET 6.0 support (@​Jevonius, #616)
  • .NET Standard 2.0 and 2.1 support (@​lg2de, #485)
  • Non-intercepted methods on a class proxy with target are now forwarded to the target (@​stakx, #571)
  • Significant performance improvements with proxy type generation for interface proxies without target. Up until now, DynamicProxy generated a separate IInvocation implementation type for every single proxied method – it is now able to reuse a single predefined type in many cases, thereby reducing the total amount of dynamic type generation. (@​stakx, #573)

Bugfixes

  • Generic method with differently named generic arguments to parent throws KeyNotFoundException (@​stakx, #106)
  • Proxying certain [Serializable] classes produces proxy types that fail PEVerify test (@​stakx, #367)
  • private protected methods are not intercepted (@​CrispyDrone, #535)
  • System.UIntPtr unsupported (@​stakx, #546)
  • DynamicProxy generates two modules when proceeding from a class proxy's protected method to the target, causing an InvalidOperationException when saving the generated assembly to disk (@​stakx, #569)
  • Upgrade log4net to v2.0.13 (@​jonorossi, @​stakx, @​dschwartzni, #574, #605)

Deprecations

  • Removed support for the .NET Framework < 4.6.2 and .NET Standard 1.x. (@​stakx, #495, #496; @​Jevonius, #614)
  • Removed support for Code Access Security (CAS). (@​stakx, #502)
  • Removed support for Remoting. This library no longer defines any types deriving from MarshalByRefObject, and ProxyUtil.IsProxy (which used to recognize remoting/"transparent" proxies) now tests only for DynamicProxy proxies. (@​stakx, #507)
  • The following public members have been removed:
    • Castle.Core.Internal.CollectionExtensions (class)
    • Castle.Core.Internal.Lock (class) along with all related types and methods
    • Castle.Core.Internal.PermissionUtil.IsGranted (method)
    • Castle.Core.Pair<,> (type). Use System.ValueTuple<,> or System.Tuple<,> instead.
    • all type members in Castle.DynamicProxy.ModuleScope that gave direct access to DynamicProxy's type cache and ModuleBuilders. Only SaveAssembly, LoadAssemblyIntoCache, and members supporting these two facilities are left public.
    • almost all types and type members in the Castle.DynamicProxy.* sub-namespaces, as most of them are intended for internal use only.
    • DynamicProxy's custom exception types have been replaced by standard BCL exceptions (where appropriate), and by a single DynamicProxyException type for internal DynamicProxy errors.

5.0.0-beta001

Full release notes will be available in the future.

4.4.1

Bugfixes

  • Prevent method name collisions when a proxy type implements more than two identically named interfaces having one or more identically named methods each. Name collisions are avoided by including the declaring types' namespaces in the proxy type's method names. (@​stakx, #469)
  • Reduce lock contention while generating new proxy types which previously blocked new proxy instances (@​tangdf, #484)
  • Fix mixins where proxy constructor fields were ordered differently to interfaces because of different case comparisons (@​zapov, #475)
  • Fix proxy generation for types having only a private protected constructor (@​mriehm, #491)
Changelog

Sourced from Castle.Core's changelog.

5.1.0 (2022-08-02)

Enhancements:

  • Support for covariant method returns (@​stakx, #619)
  • Performance improvement with proxy type generation for class proxies (without target). Abstract class methods now reuse a predefined invocation type (like methods of interface proxies without target; see explanation below at version 5.0.0 enhancements) (@​stakx, #626)

Bugfixes:

  • DynamicProxy emits invalid metadata for redeclared event (@​stakx, #590)
  • Proxies using records with a base class broken using .NET 6 compiler (@​ajcvickers, #601)
  • MissingMethodException when proxying interfaces containing sealed methods (@​stakx, #621)

5.0.0 (2022-05-11)

Enhancements:

  • .NET 6.0 support (@​Jevonius, #616)
  • .NET Standard 2.0 and 2.1 support (@​lg2de, #485)
  • Non-intercepted methods on a class proxy with target are now forwarded to the target (@​stakx, #571)
  • Significant performance improvements with proxy type generation for interface proxies without target. Up until now, DynamicProxy generated a separate IInvocation implementation type for every single proxied method – it is now able to reuse a single predefined type in many cases, thereby reducing the total amount of dynamic type generation. (@​stakx, #573)

Bugfixes:

  • Generic method with differently named generic arguments to parent throws KeyNotFoundException (@​stakx, #106)
  • Proxying certain [Serializable] classes produces proxy types that fail PEVerify test (@​stakx, #367)
  • private protected methods are not intercepted (@​CrispyDrone, #535)
  • System.UIntPtr unsupported (@​stakx, #546)
  • DynamicProxy generates two modules when proceeding from a class proxy's protected method to the target, causing an InvalidOperationException when saving the generated assembly to disk (@​stakx, #569)
  • Upgrade log4net to v2.0.13 (@​jonorossi, @​stakx, @​dschwartzni, #574, #605)

Deprecations:

  • Removed support for the .NET Framework < 4.6.2 and .NET Standard 1.x. (@​stakx, #495, #496; @​Jevonius, #614)
  • Removed support for Code Access Security (CAS). (@​stakx, #502)
  • Removed support for Remoting. This library no longer defines any types deriving from MarshalByRefObject, and ProxyUtil.IsProxy (which used to recognize remoting/"transparent" proxies) now tests only for DynamicProxy proxies. (@​stakx, #507)
  • The following public members have been removed:
    • Castle.Core.Internal.CollectionExtensions (class)
    • Castle.Core.Internal.Lock (class) along with all related types and methods
    • Castle.Core.Internal.PermissionUtil.IsGranted (method)
    • Castle.Core.Pair<,> (type). Use System.ValueTuple<,> or System.Tuple<,> instead.
    • all type members in Castle.DynamicProxy.ModuleScope that gave direct access to DynamicProxy's type cache and ModuleBuilders. Only SaveAssembly, LoadAssemblyIntoCache, and members supporting these two facilities are left public.
    • almost all types and type members in the Castle.DynamicProxy.* sub-namespaces, as most of them are intended for internal use only.
    • DynamicProxy's custom exception types have been replaced by standard BCL exceptions (where appropriate), and by a single DynamicProxyException type for internal DynamicProxy errors.

4.4.1 (2020-05-06)

Bugfixes:

  • Prevent method name collisions when a proxy type implements more than two identically named interfaces having one or more identically named methods each. Name collisions are avoided by including the declaring types' namespaces in the proxy type's method names. (@​stakx, #469)
  • Reduce lock contention while generating new proxy types which previously blocked new proxy instances (@​tangdf, #484)
  • Fix mixins where proxy constructor fields were ordered differently to interfaces because of different case comparisons (@​zapov, #475)
  • Fix proxy generation for types having only a private protected constructor (@​mriehm, #491)
Commits
  • c6d7a16 Update changelog for 5.1.0 release
  • 4b85681 Merge pull request #621 from stakx/bugfix/sealed-interface-methods
  • 4c5e227 Update the changelog
  • 9c58968 Exclude non-proxyable interface methods
  • 0fc266e MissingMethodException when proxying interface with sealed method
  • a133ee3 Merge pull request #626 from stakx/refactor/inheritance-invocation-without-ta...
  • 51894ee Update changelog
  • 3443584 Update ref/ public contract files
  • 5aa18ed Use standard invocation type for class proxy methods w/o target
  • d0c6e38 Merge pull request #619 from stakx/bugfix/covariant-returns
  • 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 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)

@dependabot dependabot bot added .NET Pull requests that update .net code dependencies Pull requests that update a dependency file labels Aug 2, 2022
@dependabot dependabot bot requested a review from JSkimming August 2, 2022 23:08
@dependabot dependabot bot force-pushed the dependabot/nuget/Castle.Core-5.1.0 branch from 8730081 to 02cb572 Compare August 10, 2022 23:15
@dependabot dependabot bot force-pushed the dependabot/nuget/Castle.Core-5.1.0 branch from 02cb572 to 3fca237 Compare August 30, 2022 23:14
@dependabot dependabot bot force-pushed the dependabot/nuget/Castle.Core-5.1.0 branch 3 times, most recently from e6207b1 to fdc9f9b Compare September 30, 2022 07:55
@dependabot dependabot bot force-pushed the dependabot/nuget/Castle.Core-5.1.0 branch 2 times, most recently from fcf265f to a778565 Compare November 2, 2022 19:04
@coveralls
Copy link

Pull Request Test Coverage Report for Build 3380372090

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 100.0%

Totals Coverage Status
Change from base Build 3380366330: 0.0%
Covered Lines: 219
Relevant Lines: 219

💛 - Coveralls

@codecov
Copy link

codecov bot commented Nov 2, 2022

Codecov Report

Merging #162 (8b1f1c8) into master (8b1f1c8) will not change coverage.
The diff coverage is n/a.

❗ Current head 8b1f1c8 differs from pull request most recent head bc39bca. Consider uploading reports for the commit bc39bca to get more accurate results

@@            Coverage Diff            @@
##            master      #162   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            5         5           
  Lines          219       219           
=========================================
  Hits           219       219           

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

@dependabot dependabot bot force-pushed the dependabot/nuget/Castle.Core-5.1.0 branch 2 times, most recently from 0ff8ebf to 8e701e9 Compare November 2, 2022 22:13
Bumps [Castle.Core](https://github.com/castleproject/Core) from 4.4.0 to 5.1.0.
- [Release notes](https://github.com/castleproject/Core/releases)
- [Changelog](https://github.com/castleproject/Core/blob/master/CHANGELOG.md)
- [Commits](castleproject/Core@v4.4.0...v5.1.0)

---
updated-dependencies:
- dependency-name: Castle.Core
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot force-pushed the dependabot/nuget/Castle.Core-5.1.0 branch from 8e701e9 to bc39bca Compare November 12, 2022 23:12
@dependabot @github
Copy link
Contributor Author

dependabot bot commented on behalf of github Jan 2, 2023

Superseded by #180.

@dependabot dependabot bot closed this Jan 2, 2023
@dependabot dependabot bot deleted the dependabot/nuget/Castle.Core-5.1.0 branch January 2, 2023 00:10
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 .NET Pull requests that update .net code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants