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

chore(deps): update all non-major dependencies #123

Merged
merged 1 commit into from
Feb 22, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 22, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
Grpc.AspNetCore 2.60.0 -> 2.61.0 age adoption passing confidence
Grpc.AspNetCore.HealthChecks 2.60.0 -> 2.61.0 age adoption passing confidence
Grpc.AspNetCore.Server.Reflection 2.60.0 -> 2.61.0 age adoption passing confidence
coverlet.collector 6.0.0 -> 6.0.1 age adoption passing confidence
coverlet.msbuild 6.0.0 -> 6.0.1 age adoption passing confidence
csharpier 0.27.2 -> 0.27.3 age adoption passing confidence

Release Notes

grpc/grpc-dotnet (Grpc.AspNetCore)

v2.61.0

What's Changed
New Contributors

Full Changelog: grpc/grpc-dotnet@v2.60.0...v2.61.0

coverlet-coverage/coverlet (coverlet.collector)

v6.0.1

Fixed
Improvements

Diff between 6.0.0 and 6.0.1

belav/csharpier (csharpier)

v0.27.3

Compare Source

What's Changed

Add more options to CodeFormatterOptions #​1172

The API for CSharpier was only exposing CodeFormatterOptions.PrintWidth. It is now in sync with the CLI and exposes all of the available options

public class CodeFormatterOptions
{
    public int Width { get; init; } = 100;
    public IndentStyle IndentStyle { get; init; } = IndentStyle.Spaces;
    public int IndentSize { get; init; } = 4;
    public EndOfLine EndOfLine { get; init; } = EndOfLine.Auto;
}

Thanks go to @​Phault for the contribution

Extra indent when call method on RawStringLiteral #​1169

When a raw string literal was the first argument to a method call, it was getting an extra indent.

// input & expected output
CallMethod(
    """
    SomeRawString
    """.CallMethod()
);

// 0.27.2
CallMethod(
    """
        SomeRawString
        """.CallMethod()
);

Thanks go to @​Rudomitori for reporting the bug.

Using aliases sorting is not always the same depending on the input order #​1168

Using aliases were not sorting properly, resulting differing outputs and unstable formatting.

Inputs of

using A = string;
using B = string;
using C = string;
using D = string;

And

using D = string;
using C = string;
using B = string;
using A = string;

Now always result in properly sorted output of

using A = string;
using B = string;
using C = string;
using D = string;

Thanks go to @​Araxor for reporting the bug.

Spread (in collection expression) are not formatted #​1167

The spread element was unformatted, and left as is. It is now formatted as follows.

int[] someArray = [.. someOtherArray];
int[] someOtherArray = [.. value1, .. value2, .. value3];

int[] someOtherArray =
[
    .. value1________________________________,
    .. value2________________________________,
    .. value3________________________________
];

Thanks go to @​jods4 for reporting the bug.

Fix empty line before collection expression in attribute #​1164

A collection expression in an attribute resulted in an extra line before the collection expression.

// input & expected output
[SomeAttribute(
    [
        someValue_______________________________________________,
        someValue_______________________________________________,

    ]
)]
class ClassName { }

// 0.27.2
[SomeAttribute(

    [
        someValue_______________________________________________,
        someValue_______________________________________________,
    ]
)]
class ClassName { }

Thanks go to @​Rudomitori for reporting the bug.

using static System.* usings not ordered before other static usings like using System.* ones #​1162

Static usings were not following the rule that System.* should be sorted to the top.

// input & expected output
using static System;
using static System.Web;
using static AWord;
using static ZWord;

// 0.27.2
using static AWord;
using static System;
using static System.Web;
using static ZWord;
Remove hash from version #​1144

When .net8 support was added, CSharpier started including a commit hash in the version number output. This was due to a breaking change in the sdk.

> dotnet csharpier --version
0.27.2+b456544aad8957d0e2026afe1a37544bb74552ba

CSharpier no longer includes the commit hash

> dotnet csharpier --version
0.27.3

Configuration

📅 Schedule: Branch creation - "before 4am on the first day of the month" (UTC), 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.

Copy link

github-actions bot commented Feb 22, 2024

Code Coverage

Package Line Rate Branch Rate Health
Vfps.Tests 99% 100%
Vfps 94% 60%
Summary 95% (442 / 463) 66% (33 / 50)

Minimum allowed line rate is 50%


ghz run statistics

Summary:
  Count:	5000
  Total:	9.48 s
  Slowest:	515.89 ms
  Fastest:	5.00 ms
  Average:	91.85 ms
  Requests/sec:	527.28

Response time histogram:
  4.999   [1]    |
  56.088  [379]  |∎∎∎∎
  107.177 [3636] |∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎∎
  158.266 [796]  |∎∎∎∎∎∎∎∎∎
  209.355 [134]  |∎
  260.443 [4]    |
  311.532 [0]    |
  362.621 [0]    |
  413.710 [1]    |
  464.799 [0]    |
  515.887 [49]   |∎

Latency distribution:
  10 % in 58.25 ms 
  25 % in 67.85 ms 
  50 % in 87.31 ms 
  75 % in 103.09 ms 
  90 % in 119.36 ms 
  95 % in 135.01 ms 
  99 % in 212.67 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) | 15.92
  grpc/latency/p99 (msec)  | 57.00
  grpc/request-count       | 50000.00
  

Copy link

🦙 MegaLinter status: ⚠️ WARNING

Descriptor Linter Files Fixed Errors Elapsed time
✅ ACTION actionlint 9 0 0.2s
✅ CSHARP csharpier 46 0 3.05s
⚠️ CSHARP dotnet-format 46 46 85.08s
⚠️ CSHARP roslynator 5 5 40.58s
✅ DOCKERFILE hadolint 1 0 0.16s
✅ EDITORCONFIG editorconfig-checker 105 0 0.47s
✅ JSON eslint-plugin-jsonc 9 0 1.33s
✅ JSON jsonlint 9 0 0.22s
✅ JSON prettier 9 0 0.8s
✅ JSON v8r 9 0 6.16s
✅ MARKDOWN markdownlint 3 0 0.66s
⚠️ MARKDOWN markdown-table-formatter 3 1 0.38s
✅ PROTOBUF protolint 5 0 4.34s
✅ REPOSITORY checkov yes no 14.36s
✅ REPOSITORY dustilock yes no 0.03s
✅ REPOSITORY gitleaks yes no 0.19s
✅ REPOSITORY git_diff yes no 0.02s
✅ REPOSITORY grype yes no 14.0s
✅ REPOSITORY kics yes no 20.69s
✅ REPOSITORY secretlint yes no 1.11s
✅ REPOSITORY syft yes no 0.51s
✅ REPOSITORY trivy yes no 7.0s
✅ REPOSITORY trivy-sbom yes no 2.07s
✅ REPOSITORY trufflehog yes no 10.68s
✅ XML xmllint 1 0 0.02s
✅ YAML prettier 24 0 1.54s
✅ YAML v8r 24 0 23.18s
✅ YAML yamllint 24 0 0.68s

See detailed report in MegaLinter reports

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

MegaLinter is graciously provided by OX Security

@chgl chgl merged commit aa1198c into master Feb 22, 2024
17 checks passed
@renovate renovate bot deleted the renovate/all-minor-patch branch February 22, 2024 14:15
@miracum-bot miracum-bot mentioned this pull request Feb 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant