Bump NSwag.AspNetCore from 14.6.1 to 14.6.3

[dependabot]

Updated NSwag.AspNetCore from 14.6.1 to 14.6.3.

Release notes

Sourced from NSwag.AspNetCore's releases.

14.6.3

What's Changed

• Using final .NET 10 libraries/SDK and minor .NET 10 fixes (v14.6.3) by @​RicoSuter in Minor .NET 10 fixes (v14.6.3) RicoSuter/NSwag#5307
• Updated packages for CVE-2025-55315 by @​erjdev in Updated packages for CVE-2025-55315 RicoSuter/NSwag#5299
• fix: nswag.js try detect the runtime version from config file by @​dylanvdmerwe in fix: nswag.js try detect the runtime version from config file RicoSuter/NSwag#5302

New Contributors

• @​erjdev made their first contribution in Updated packages for CVE-2025-55315 RicoSuter/NSwag#5299
• @​dylanvdmerwe made their first contribution in fix: nswag.js try detect the runtime version from config file RicoSuter/NSwag#5302

Full Changelog: RicoSuter/NSwag@v14.6.2...v14.6.3

14.6.2

Fixes EnumValue regression in v14.6.1 by introducing a new JsonLibraryVersion configuration (default 8.0)

What's Changed

• v14.6.2: Update NJS and update commands/UI & update .NET 10 SDK (RC2) by @​RicoSuter in v14.6.2: Update NJS and update commands/UI & update .NET 10 SDK (RC2) RicoSuter/NSwag#5298
• Update NJsonSchema to v11.5.2 (with revert to previous EnumValue behavior and new config)
  • https://github.com/RicoSuter/NJsonSchema/releases/tag/v11.5.2

Full Changelog: RicoSuter/NSwag@v14.6.1...v14.6.2

Commits viewable in compare view.

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)

[github-actions]

Ollama Code Review for AspNetCoreSerilog/AspNetCoreSerilog.csproj:\n\nCode Review and Suggestions

The provided XML file appears to be a .csproj file, which is the build configuration file for .NET projects. Here are some suggestions for improvement:

1. Separate Configuration Settings from Package References: The <PropertyGroup> section contains configuration settings such as the target framework, Docker default OS, and language version. Consider moving these settings to a separate appsettings.json or config.json file.

2. Use Meaningful Property Names: Instead of using short property names like UserSecretsId, consider using more descriptive names like AzureAppSecretId.

3. Specify NuGet Package Versions: The package references are specified without version numbers, which can lead to compatibility issues if different versions of the same package are used in different projects.

4. Consider Using a Consistent Formatting Style: The XML file appears to be formatted using the standard .NET framework formatting style. However, it's always a good practice to use a consistent formatting style throughout the project.

5. Add Comments or Documentation: Adding comments or documentation can improve readability and make the code more maintainable.

Improved Code

Here is an improved version of the provided XML file:

<Project Sdk="Microsoft.NET.Sdk.Web">

  <!-- Configuration Settings -->
  <PropertyGroup>
    <TargetFramework>net8.0</TargetFramework>
    <AzureAppSecretId>9d750d08-73ae-4876-83cc-4aad393eef18</AzureAppSecretId>
    <DockerDefaultTargetOS>Linux</DockerDefaultTargetOS>
    <LangVersion>default</LangVersion>
  </PropertyGroup>

  <!-- NuGet Package References -->
  <ItemGroup>
    <PackageReference Include="Microsoft.AspNetCore.Authentication" Version="2.3.0" />
    <PackageReference Include="Microsoft.AspNetCore.Authentication.JwtBearer" Version="8.0.21" />
    <PackageReference Include="NSwag.AspNetCore" Version="14.6.3" />
    <PackageReference Include="Serilog.AspNetCore" Version="9.0.0" />
    <PackageReference Include="Serilog.Enrichers.Environment" Version="3.0.1" />
    <PackageReference Include="Serilog.Enrichers.Thread" Version="4.0.0" />
  </ItemGroup>

</Project>

Best Practices and Readability

To improve readability, consider the following best practices:

1. Use Meaningful Variable Names: Use descriptive variable names to make the code more readable.

2. Add Comments or Documentation: Add comments or documentation to explain complex logic or algorithms.

3. Format Consistently: Use a consistent formatting style throughout the project.

4. Organize Code into Logical Sections: Organize the code into logical sections, such as properties and methods.

5. Consider Using a Code Analysis Tool: Consider using a code analysis tool like SonarQube or Code Analysis to identify potential issues with the code.

[github-actions]

Ollama Code Review for AspNetCoreSerilog/AspNetCoreSerilog.csproj:\n\nThe provided code snippet appears to be a Visual Studio Project file (.csproj) for an ASP.NET Web application. Here are some suggestions for improvement, coding best practices, readability, and maintainability:

1. Follow PEP 8 (Python Enhancement Proposal 8): Although this is a C# project file, I'll suggest improvements in line with Python's style guide.

   • Use consistent indentation (4 spaces).
   • Use meaningful variable names.
   • Avoid unnecessary white space at the end of lines.

2. Use Meaningful Property Names:

   • Instead of <TargetFramework>net8.0</TargetFramework>, consider using a more descriptive name like <TargetFrameworkVersion>net8.0</TargetFrameworkVersion>.

3. Group Related Settings Together:

   • Move all PackageReference elements into separate <ItemGroup> sections, each with a clear purpose (e.g., "Authentication Packages," "Logging Packages," etc.).

4. Use a Consistent Order for Property Groups and ItemGroups:

   • Typically, the project properties come before any groupings of items (e.g., files, packages).

Here's an improved version of your code snippet:

<Project Sdk="Microsoft.NET.Sdk.Web">
    <PropertyGroup>
        <!-- Target framework -->
        <TargetFrameworkVersion>net8.0</TargetFrameworkVersion>

        <!-- User secrets ID -->
        <UserSecretsId>9d750d08-73ae-4876-83cc-4aad393eef18</UserSecretsId>

        <!-- Docker default target OS -->
        <DockerDefaultTargetOS>Linux</DockerDefaultTargetOS>

        <!-- Language version -->
        <LangVersion>default</LangVersion>
    </PropertyGroup>

    <!-- Authentication Packages -->
    <ItemGroup>
        <PackageReference Include="Microsoft.AspNetCore.Authentication" Version="2.3.0" />
        <PackageReference Include="Microsoft.AspNetCore.Authentication.JwtBearer" Version="8.0.22" />
    </ItemGroup>

    <!-- Logging Packages -->
    <ItemGroup>
        <PackageReference Include="NSwag.AspNetCore" Version="14.6.3" />
        <PackageReference Include="Serilog.AspNetCore" Version="9.0.0" />
        <PackageReference Include="Serilog.Enrichers.Environment" Version="3.0.1" />
        <PackageReference Include="Serilog.Enrichers.Thread" Version="4.0.0" />
    </ItemGroup>
</Project>

This improved version follows PEP 8 guidelines and reorganizes the code to be more readable and maintainable.