chore(deps): update all non-major dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence	Type	Update
EFCore.NamingConventions	8.0.2 -> 8.0.3					nuget	patch
Hl7.Fhir.R4	5.5.0 -> 5.5.1					nuget	patch
NBomber	5.4.1 -> 5.5.0					nuget	minor
csharpier	0.26.7 -> 0.27.2					nuget	minor
docker.io/bitnami/kubectl	1.29.0 -> 1.29.1					final	patch
xunit	2.6.5 -> 2.6.6					nuget	patch

---

Release Notes

efcore/EFCore.NamingConventions (EFCore.NamingConventions)

v8.0.3: Version 8.0.3

This releases three additional issues in the 8.0 release.

FirelyTeam/firely-net-sdk (Hl7.Fhir.R4)

v5.5.1: 5.5.1

Intro:

Hotfix release.
This release solves a race condition that occurred when expanding ValueSets using the LocalTerminologyService.

Changes:

• #​2666: Fix race condition around expanding a valueset + unit test.
• #​2665: Add Async support for SnapshotSource STU3

This list of changes was auto generated.

PragmaticFlow/NBomber (NBomber)

v5.5.0: NBomber v5.5.0 - WebSockets

Changes:

• Add API for scenario distribution Zipfan, Multinomial, Uniform

• Add Single-file deployment support

• Fixed issue with log file > 1GB

• Add NBomber.WebSockets plugin

Docs updates:

• Dynamic workloads
• WebSockets
• NBomber.Data

New examples:

• Dynamic worloads

• Data examples

• WebSockets

belav/csharpier (csharpier)

v0.27.2

Compare Source

What's Changed

Orphan variable since 0.27.1 #​1153

0.27.1 introduced the following formatting regression, resulting in short variables being orphaned on a line

// 0.27.1
o
    .Property.CallMethod(
        someParameter_____________________________,
        someParameter_____________________________
    )
    .CallMethod()
    .CallMethod();

// 0.27.2
o.Property.CallMethod(
    someParameter_____________________________,
    someParameter_____________________________
)
    .CallMethod()
    .CallMethod();

Thanks go to @​aurnoi1 for reporting the bug

Better support for CSharp Script #​1141

Version 0.27.1 parsed .csx files as if they were C#, so it could only format simple ones. It now parses them as CSharpScript files so it can format them properly.

Thanks go to @​Eptagone for reporting the bug.

Full Changelog: belav/csharpier@0.27.1...0.27.2

v0.27.1

Compare Source

What's Changed

Support for CSharp Script #​1141

Previously CSharpier would only format files matching *.cs which prevented it from formatting C# script files. It now formats *.{cs,csx}

Thanks go to @​Eptagone for the suggestion

Weird formatting of invocation chain #​1130

Invocation chains that started with an identifier <= 4 characters were causing a strange break in the first method call. There were other edge cases cleaned up while working on the fix.

// 0.27.0
var something________________________________________ = x.SomeProperty.CallMethod(
    longParameter_____________,
    longParameter_____________
)
    .CallMethod();

// 0.27.1
var something________________________________________ = x
    .SomeProperty.CallMethod(longParameter_____________, longParameter_____________)
    .CallMethod();

// 0.27.0
var someLongValue_________________ = memberAccessExpression[
    elementAccessExpression
].theMember______________________________();

// 0.27.1
var someLongValue_________________ = memberAccessExpression[elementAccessExpression]
    .theMember______________________________();

// 0.27.0
someThing_______________________
    ?.Property
    .CallMethod__________________()
    .CallMethod__________________();

// 0.27.1
someThing_______________________
    ?.Property.CallMethod__________________()
    .CallMethod__________________();

Thanks go to @​Rudomitori for reporting the issue

"Failed syntax tree validation" for raw string literals #​1129

When an interpolated raw string changed indentation due to CSharpier formatting, CSharpier was incorrectly reporting it as failing syntax tree validation.

// input
CallMethod(CallMethod(
   $$"""
   SomeString
   """, someValue));

// output
CallMethod(
    CallMethod(
        $$"""
        SomeString
        """,
        someValue
    )
);

Thanks go to @​Rudomitori for reporting the issue

Adding experimental support using HTTP for the extensions to communicate with CSharpier #​1137

The GRPC support added in 0.27.0 increased the size of the nuget package significantly and has been removed.

CSharpier can now start a kestrel web server to support communication with the extensions once they are all updated.

Full Changelog: belav/csharpier@0.27.0...0.27.1

v0.27.0

Compare Source

What's Changed

Improve formatting of lambda expressions #​1066

Many thanks go to @​Rudomitori for contributing a number of improvements to the formatting of lambda expressions.

Some examples of the improvements.

// input
var affectedRows = await _dbContext.SomeEntities
    .ExecuteUpdateAsync(
        x => 
            x.SetProperty(x => x.Name, x => command.NewName)
                .SetProperty(x => x.Title, x => command.NewTItle)
                .SetProperty(x => x.Count, x => x.Command.NewCount)
    );

// 0.27.0
var affectedRows = await _dbContext.SomeEntities
    .ExecuteUpdateAsync(x =>
        x.SetProperty(x => x.Name, x => command.NewName)
            .SetProperty(x => x.Title, x => command.NewTItle)
            .SetProperty(x => x.Count, x => x.Command.NewCount)
    );

// input
builder.Entity<IdentityUserToken<string>>(b =>
{
    b.HasKey(
        l =>
            new
            {
                l.UserId,
                l.LoginProvider,
                l.Name
            }
    );
    b.ToTable("AspNetUserTokens");
});

// 0.27.0
builder.Entity<IdentityUserToken<string>>(b =>
{
    b.HasKey(l => new
    {
        l.UserId,
        l.LoginProvider,
        l.Name
    });
    b.ToTable("AspNetUserTokens");
});

// input
table.PrimaryKey(
    "PK_AspNetUserTokens",
    x =>
        new
        {
            x.UserId,
            x.LoginProvider,
            x.Name
        }
);

// 0.27.0
table.PrimaryKey(
    "PK_AspNetUserTokens",
    x => new
    {
        x.UserId,
        x.LoginProvider,
        x.Name
    }
);

readonly ref is changed to ref readonly causing error CS9190 #​1123

CSharpier was sorting modifiers in all places they occurred. Resulting the following change that led to code that would not compile.

// input
void Method(ref readonly int someParameter) { }

// 0.26.7
void Method(readonly ref int someParameter) { }

// 0.27.0
void Method(ref readonly int someParameter) { }

Thanks go to @​aurnoi1 for reporting the bug

#if at the end of collection expression gets eaten #​1119

When a collection expression contained a directive immediately before the closing bracket, that directive was not included in the output.

// input
int[] someArray =
[
    1

#if DEBUG
    ,
    2

#endif
];

// 0.26.7
int[] someArray = [1];

// 0.27.0
int[] someArray =
[
    1

#if DEBUG
    ,
    2

#endif
];

Thanks go to @​Meowtimer for reporting the bug

CSharpier.MsBuild - Set Fallback for dotnetcore3.1 or net5.0 applications #​1111

CSharpier.MsBuild made an assumption that the project being built would be built using net6-net8 and failed when the project was built with earlier versions of dotnet.

It now falls back to trying to use net8

Thanks go to @​samtrion for the contribution

Allow empty/blank lines in object initializers #​1110

Large object initializers now retain single empty lines between initializers.

vvar someObject = new SomeObject
{
    NoLineAllowedAboveHere = 1,

    ThisLineIsOkay = 2,

    // comment
    AndThisLine = 3,
    DontAddLines = 4,
};

Thanks go to @​Qtax for the suggestion

Add option to allow formatting auto generated files. [#​1055][https://github.com/belav/csharpier/issues/1055](https://togithub.com/belav/csharpier/issues/1055)5

By default CSharpier will not format files that were generated by the SDK, or files that begin with <autogenerated /> comments.

Passing the option --include-generated to the CLI will cause those files to be formatted.

Format raw string literals indentation #​975

CSharpier now adjusts the indentation of raw string literals if the end delimiter is indented.

// input
var someString = """
            Indent based on previous line
            """;

var doNotIndentIfEndDelimiterIsAtZero = """
Keep This
    Where It
Is
""";

// 0.26.7
var someString = """
            Indent based on previous line
            """;

var doNotIndentIfEndDelimiterIsAtZero = """
Keep This
    Where It
Is
""";

// 0.27.0
var someString = """
    Indent based on previous line
    """;

var doNotIndentIfEndDelimiterIsAtZero = """
Keep This
    Where It
Is
""";

Thanks go to @​jods4 for reporting the issue

Incorrect indentation on a multi-line statement split by comments [#​968][https://github.com/belav/csharpier/issues/968](https://togithub.com/belav/csharpier/issues/968)8

CSharpier was not properly indenting an invocation chain when it was being split by comments.

// input
var someValue =
    // Some Comment
    CallSomeMethod()
        // Another Comment
        .CallSomeMethod();

// 0.26.7
var someValue =
// Some Comment
CallSomeMethod()
    // Another Comment
    .CallSomeMethod();

// 0.27.0
var someValue =
    // Some Comment
    CallSomeMethod()
        // Another Comment
        .CallSomeMethod();

Thanks go to @​tyrrrz for reporting the issue

Adding experimental support for GRPC for the extensions to communicate with CSharpier #​944

Currently the extensions for CSharpier send data to a running instance of CSharpier by piping stdin/stdout back and forth. This approach has proved problematic and hard to extend.

As of 0.27.0, CSharpier can run a GRPC server to allow communication with the extensions once they are all updated.

Full Changelog: belav/csharpier@0.26.7...0.27.0

xunit/xunit (xunit)

v2.6.6

Compare Source

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[github-actions]

🦙 MegaLinter status: ⚠️ WARNING

Descriptor	Linter	Files	Fixed	Errors	Elapsed time
✅ ACTION	actionlint	9		0	0.17s
⚠️ CSHARP	csharpier	46		1	2.57s
⚠️ CSHARP	dotnet-format	46		46	86.49s
⚠️ CSHARP	roslynator	5		5	42.86s
✅ DOCKERFILE	hadolint	1		0	0.09s
✅ EDITORCONFIG	editorconfig-checker	105		0	0.21s
✅ JSON	eslint-plugin-jsonc	9		0	0.91s
✅ JSON	jsonlint	9		0	0.14s
✅ JSON	prettier	9		0	0.66s
✅ JSON	v8r	9		0	5.21s
✅ MARKDOWN	markdownlint	3		0	0.93s
⚠️ MARKDOWN	markdown-table-formatter	3		1	0.29s
✅ PROTOBUF	protolint	5		0	3.67s
✅ REPOSITORY	checkov	yes		no	14.63s
✅ REPOSITORY	dustilock	yes		no	0.01s
✅ REPOSITORY	gitleaks	yes		no	0.15s
✅ REPOSITORY	git_diff	yes		no	0.04s
✅ REPOSITORY	grype	yes		no	15.05s
✅ REPOSITORY	kics	yes		no	20.97s
✅ REPOSITORY	secretlint	yes		no	0.98s
✅ REPOSITORY	syft	yes		no	0.28s
✅ REPOSITORY	trivy	yes		no	6.92s
✅ REPOSITORY	trivy-sbom	yes		no	3.81s
✅ REPOSITORY	trufflehog	yes		no	6.73s
✅ XML	xmllint	1		0	0.01s
✅ YAML	prettier	24		0	1.72s
✅ YAML	v8r	24		0	22.52s
✅ YAML	yamllint	24		0	0.57s

See detailed report in MegaLinter reports

You could have same capabilities but better runtime performances if you request a new MegaLinter flavor.

• Click here to request the new flavor

MegaLinter is graciously provided by

[github-actions]

Package	Line Rate	Branch Rate	Health
Vfps	90%	60%	✔
Vfps.Tests	99%	100%	✔
Summary	92% (453 / 492)	66% (33 / 50)	✔

Minimum allowed line rate is 50%

---

iter8 report

Experiment summary:
*******************

  Experiment completed: true
  No task failures: true
  Total number of tasks: 6
  Number of completed tasks: 6
  Number of completed loops: 1

Whether or not service level objectives (SLOs) are satisfied:
*************************************************************

  SLO Conditions                 | Satisfied
  --------------                 | ---------
  grpc/error-rate <= 0           | true
  grpc/latency/mean (msec) <= 50 | true
  grpc/latency/p99 (msec) <= 100 | true
  

Latest observed values for metrics:
***********************************

  Metric                   | value
  -------                  | -----
  grpc/error-count         | 0.00
  grpc/error-rate          | 0.00
  grpc/latency/mean (msec) | 16.28
  grpc/latency/p99 (msec)  | 58.00
  grpc/request-count       | 50000.00
  

---

ghz run statistics

Summary:
  Count:	5000
  Total:	9.02 s
  Slowest:	452.71 ms
  Fastest:	8.52 ms
  Average:	87.21 ms
  Requests/sec:	554.19

Response time histogram:
  8.522   [1]    |
  52.941  [470]  |∎∎∎∎∎∎
  97.359  [3351] |∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎
  141.777 [959]  |∎∎∎∎∎∎∎∎∎∎∎
  186.195 [148]  |∎∎
  230.614 [21]   |
  275.032 [0]    |
  319.450 [1]    |
  363.868 [0]    |
  408.287 [0]    |
  452.705 [49]   |∎

Latency distribution:
  10 % in 53.89 ms 
  25 % in 68.68 ms 
  50 % in 83.36 ms 
  75 % in 96.11 ms 
  90 % in 115.05 ms 
  95 % in 135.11 ms 
  99 % in 206.66 ms 

Status code distribution:
  [OK]   5000 responses   

---

iter8 report

Experiment summary:
*******************

  Experiment completed: true
  No task failures: true
  Total number of tasks: 6
  Number of completed tasks: 6
  Number of completed loops: 1

Whether or not service level objectives (SLOs) are satisfied:
*************************************************************

  SLO Conditions                 | Satisfied
  --------------                 | ---------
  grpc/error-rate <= 0           | true
  grpc/latency/mean (msec) <= 50 | true
  grpc/latency/p99 (msec) <= 100 | true
  

Latest observed values for metrics:
***********************************

  Metric                   | value
  -------                  | -----
  grpc/error-count         | 0.00
  grpc/error-rate          | 0.00
  grpc/latency/mean (msec) | 16.89
  grpc/latency/p99 (msec)  | 61.00
  grpc/request-count       | 50000.00
  

---

iter8 report

Experiment summary:
*******************

  Experiment completed: true
  No task failures: true
  Total number of tasks: 6
  Number of completed tasks: 6
  Number of completed loops: 1

Whether or not service level objectives (SLOs) are satisfied:
*************************************************************

  SLO Conditions                 | Satisfied
  --------------                 | ---------
  grpc/error-rate <= 0           | true
  grpc/latency/mean (msec) <= 50 | true
  grpc/latency/p99 (msec) <= 100 | true
  

Latest observed values for metrics:
***********************************

  Metric                   | value
  -------                  | -----
  grpc/error-count         | 0.00
  grpc/error-rate          | 0.00
  grpc/latency/mean (msec) | 16.31
  grpc/latency/p99 (msec)  | 65.00
  grpc/request-count       | 50000.00