Bump Microsoft.EntityFrameworkCore.InMemory from 6.0.8 to 7.0.10 #328

dependabot · 2023-08-09T03:48:52Z

Bumps Microsoft.EntityFrameworkCore.InMemory from 6.0.8 to 7.0.10.

Release notes

Sourced from Microsoft.EntityFrameworkCore.InMemory's releases.

.NET 7.0.10

Release

.NET 7.0.9

Release

EF Core 7.0.8

This is a patch release of EF Core 7.0 containing only updates to dependencies. There are no additional fixes in this release beyond those already shipped in EF Core 7.0.7.

EF Core 7.0.7 is available on NuGet now. This is a patch release of EF Core 7 containing only important bug fixes:

IndexOutOfRangeException in CreateNavigationExpansionExpression

Linq select cannot project an entity containing both Json columns and ICollections

Json: updating property with conversion from string to other type fails on sql server

Duplicate table alias in generated select query (An item with the same key has already been added)

InvalidOperationException when calling ExecuteUpdate with owned entity & using current value

Query/Json: projecting entity collection along with json collection generates invalid shaper

AutoInclude causes ExecuteDelete to fail

Multiple LeftJoins (GroupJoins) lead to GroupJoin Exception when the same where is used twice

SaveChanges circular dependency in unique unfiltered index (when change doesn't affect any column from unique index).

EF Core 7.0.5 is available on NuGet now. This is a patch release of EF Core 7 containing only important bug fixes:

Can't add migration renaming a column on TPC root

Scaffolded collection navigation properties do not have setters

EF7 generating incorrect SQL for the Concat/Union All

Added nullable property to Json mapped model resulting in errors instead of mapping non existing json property to null

EF Core 7.0.4

This is a patch release of EF Core 7.0 containing only important bug fixes:

Exception replacing multi-level relationship in EF7

Deletion can cause error "The association between entity types A and B has been severed..."

Non-empty second migration in TPC scheme using inheritance

Entity Framework Core 7 keeps creating the same migration for Nullable DateTime field

TPC mapping strategy not respecting default database schema during migration

Count after Take throws "No column name was specified for column 1 of 't'."

And for Microsoft.Data.Sqlite:

ArgumentOutOfRangeException in SqliteConnectionFactory.PruneCallback

EF Core 7.0.3

This is a patch release of EF Core 7.0 containing only important bug fixes:

Add-Migration fails with "An item with the same key has already been added" when renaming entity

ExecuteUpdate fails when target entity has an owned entity

EF Core 7 Rev eng: Missing HasForeignKey when referencing a navigation property with a unique constraint with DataAnnotations on

Change in behaviour of CSharpHelper.Identifier(string name)

... (truncated)

Commits

8907538 Merge in 'release/7.0' changes
3577954 Update dependencies from https://github.com/dotnet/arcade build 20230711.2 (#...
a4937ab Merge in 'release/7.0' changes
ec96a9a Merge pull request #31225 from vseanreesermsft/internal-merge-7.0-2023-07-11-...
c178722 Update global.json
56dc4c2 Update global.json
d14f37e Merge commit 'e00be013488a9a56a0e29230be0fe10026dbb209' into internal-merge-7...
52e1a71 Merge in 'release/7.0' changes
2669b8e Merge in 'release/7.0' changes
bbc6340 Merge branch 'release/6.0' into release/7.0
Additional commits viewable in compare view

You can trigger a rebase of this PR 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)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

Bumps [Microsoft.EntityFrameworkCore.InMemory](https://github.com/dotnet/efcore) from 6.0.8 to 7.0.10. - [Release notes](https://github.com/dotnet/efcore/releases) - [Commits](dotnet/efcore@v6.0.8...v7.0.10) --- updated-dependencies: - dependency-name: Microsoft.EntityFrameworkCore.InMemory dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>

pull-request-quantifier-deprecated · 2023-08-09T03:48:56Z

This PR has 4 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

Quantification details

Label      : Extra Small
Size       : +2 -2
Percentile : 1.6%

Total files changed: 1

Change summary by file extension:
.csproj : +2 -2

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

Fast and predictable releases to production:
- Optimal size changes are more likely to be reviewed faster with fewer
  iterations.
- Similarity in low PR complexity drives similar review times.
Review quality is likely higher as complexity is lower:
- Bugs are more likely to be detected.
- Code inconsistencies are more likely to be detected.
Knowledge sharing is improved within the participants:
- Small portions can be assimilated better.
Better engineering practices are exercised:
- Solving big problems by dividing them in well contained, smaller problems.
- Exercising separation of concerns within the code changes.

What can I do to optimize my changes

Use the PullRequestQuantifier to quantify your PR accurately
- Create a context profile for your repo using the context generator
- Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
- Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
- Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
Change your engineering behaviors
- For PRs that fall outside of the desired spectrum, review the details and check if:
  - Your PR could be split in smaller, self-contained PRs instead
  - Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

One line was added: +1 -0
One line was deleted: +0 -1
One line was modified: +1 -1 (git diff doesn't know about modified, it will
interpret that line like one addition plus one deletion)
Change percentiles: Change characteristics (addition, deletion, modification)
of this PR in relation to all other PRs within the repository.

Was this comment helpful? 👍 :ok_hand: :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.