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 Riok.Mapperly from 3.3.0 to 3.4.0 #67

Closed
wants to merge 1 commit into from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Feb 26, 2024

Bumps Riok.Mapperly from 3.3.0 to 3.4.0.

Release notes

Sourced from Riok.Mapperly's releases.

v3.4.0

3.4.0 (2024-02-23)

Bug Fixes

  • correctly annotate nullable generics in disabled nullable contexts (#1020) (d35c52d)
  • do not resolve existing one sideded loose nullable property mappings (#1090) (7998720)
  • don't diagnostic for constructor mappings when no instance can be created but none is needed anyway (450d7ca)
  • generate enumerable mapping methods with interface parameters instead of concrete types to reduce generated methods (#1088) (66752cf)
  • generate generic mapping only for matching source / target types if non-generic (#1000) (9a2916f)
  • handle nullable correctly in nullable disabled contexts for generics and arrays (#1029) (132b8cc)
  • prevent collection mapping from using invalid length property (#1108) (216f791)
  • prevent crash for delegate fields when deep mapping is enabled (#1058) (88dd1ff)
  • remove Runtime suffix of MapperlyAbstractionsScope msbuild option (#1049) (54b0eea)
  • upgrade parameter nullability correctly (#1057) (ad917ee)
  • use correct argument types in user defined enumerable mappings with an array source parameter (#1125) (8b14725)

Features

  • add option to prefer parameterised constructors (#1061) (e606f93)
  • annotate all emitted methods and classes with GeneratedCodeAttribute. (#1069) (374e6cb)
  • remove runtime dependency (#1027) (ca3ea5a)

v3.4.0-next.5

3.4.0-next.5 (2024-02-20)

Bug Fixes

  • use correct argument types in user defined enumerable mappings with an array source parameter (#1125) (8b14725)

v3.4.0-next.4

3.4.0-next.4 (2024-02-16)

Bug Fixes

  • don't diagnostic for constructor mappings when no instance can be created but none is needed anyway (450d7ca)
  • prevent collection mapping from using invalid length property (#1108) (216f791)

v3.4.0-next.3

3.4.0-next.3 (2024-02-05)

Bug Fixes

  • do not resolve existing one sideded loose nullable property mappings (#1090) (7998720)
  • generate enumerable mapping methods with interface parameters instead of concrete types to reduce generated methods (#1088) (66752cf)

... (truncated)

Commits
  • 8b14725 fix: use correct argument types in user defined enumerable mappings with an a...
  • 8d66715 chore(deps): Bump csharpier from 0.27.2 to 0.27.3 (#1121)
  • 75a60a8 chore(deps): Bump Meziantou.Analyzer from 2.0.141 to 2.0.142 (#1122)
  • d51d73b chore(deps-dev): Bump @​types/react from 18.2.48 to 18.2.57 in /docs (#1124)
  • 57456a5 chore(deps): Bump NuGet.Frameworks from 6.8.0 to 6.9.1 (#1123)
  • 450d7ca fix: don't diagnostic for constructor mappings when no instance can be create...
  • 7429bc7 chore(deps): Bump Meziantou.Analyzer from 2.0.139 to 2.0.141 (#1115)
  • 8e84ac6 chore(deps): Bump Meziantou.Polyfill from 1.0.33 to 1.0.34 (#1116)
  • 5e11f6a chore(deps): Bump Microsoft.Build.Locator from 1.6.10 to 1.7.1 (#1114)
  • 94a26ef chore(deps): Bump @​mdx-js/react from 3.0.0 to 3.0.1 in /docs (#1113)
  • 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 [Riok.Mapperly](https://github.com/riok/mapperly) from 3.3.0 to 3.4.0.
- [Release notes](https://github.com/riok/mapperly/releases)
- [Changelog](https://github.com/riok/mapperly/blob/main/.releaserc.yaml)
- [Commits](riok/mapperly@v3.3.0...v3.4.0)

---
updated-dependencies:
- dependency-name: Riok.Mapperly
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Feb 26, 2024
Copy link
Contributor Author

dependabot bot commented on behalf of github Apr 8, 2024

Superseded by #74.

@dependabot dependabot bot closed this Apr 8, 2024
@dependabot dependabot bot deleted the dependabot/nuget/Riok.Mapperly-3.4.0 branch April 8, 2024 01:37
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.

None yet

0 participants