Bump Microsoft.AspNetCore.Authentication.JwtBearer from 8.0.25 to 8.0.26

[dependabot]

Updated Microsoft.AspNetCore.Authentication.JwtBearer from 8.0.25 to 8.0.26.

Release notes

Sourced from Microsoft.AspNetCore.Authentication.JwtBearer's releases.

8.0.26

Release

What's Changed

• [release/8.0] Update branding to 8.0.26 by @​vseanreesermsft in [release/8.0] Update branding to 8.0.26 dotnet/aspnetcore#65635
• [release/8.0] (deps): Bump src/submodules/googletest from 56efe39 to 73a63ea by @​dependabot[bot] in [release/8.0] (deps): Bump src/submodules/googletest from 56efe39 to 73a63ea dotnet/aspnetcore#65586
• [release/8.0] Update dependencies from dotnet/arcade by @​dotnet-maestro[bot] in [release/8.0] Update dependencies from dotnet/arcade dotnet/aspnetcore#65581
• [release/8.0] Update dependencies from dotnet/source-build-reference-packages by @​dotnet-maestro[bot] in [release/8.0] Update dependencies from dotnet/source-build-reference-packages dotnet/aspnetcore#65621
• [release/8.0] Update dependencies from dotnet/source-build-externals by @​dotnet-maestro[bot] in [release/8.0] Update dependencies from dotnet/source-build-externals dotnet/aspnetcore#65615
• Merging internal commits for release/8.0 by @​vseanreesermsft in Merging internal commits for release/8.0 dotnet/aspnetcore#65730

Full Changelog: dotnet/aspnetcore@v8.0.25...v8.0.26

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 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\nThe code provided appears to be a C# project file (.csproj) for a .NET 8.0 web application that uses Docker and various packages for authentication and logging. Here are some suggestions for improvement, coding best practices, readability, and maintainability:

1. Comments: The file is missing comments. Adding comments can help explain the purpose of each section and provide context for other developers.

2. Package Management:

   • Instead of hardcoding package versions in the PackageReference elements, consider using the PackageVersion parameter in the .csproj file or a separate appsettings.json file for easier maintenance and version management.
   • Consider using a NuGet package manager like dotnet add package to manage dependencies.

3. Consistent Spacing:

   • Some lines have inconsistent spacing (e.g., between <TargetFramework> and <UserSecretsId>, and between <ItemGroup> and its elements). Use a consistent number of spaces or consider using an auto-formatting tool for C# files.

4. Property Group Order:

   • The Project element can have multiple nested elements in any order. For better readability, group related properties together.

5. Docker Configuration:

   • Consider separating Docker configuration from the project file to improve maintainability and reusability.
   • You might also want to consider using a different approach for handling Docker configurations, such as storing it in an environment variable or a separate config file.

6. LangVersion:

   • The LangVersion property should match the version of the .NET SDK being used. Make sure to use the correct version according to your project's requirements.

7. Code Style:

   • Consider following Pylint and SonarQube guidelines for code style, which include formatting suggestions for better readability.

Here is an updated version incorporating these suggestions:

<Project Sdk="Microsoft.NET.Sdk.Web">
    <!-- Properties related to target framework -->
    <PropertyGroup>
        <TargetFramework>net8.0</TargetFramework>
        <LangVersion>latest</LangVersion> <!-- Adjust LangVersion according to your project needs -->
    </PropertyGroup>

    <!-- Package references for authentication and logging -->
    <ItemGroup>
        <PackageReference Include="Microsoft.AspNetCore.Authentication" Version="${authVersion}" />
        <PackageReference Include="Microsoft.AspNetCore.Authentication.JwtBearer" Version="${jwtVersion}" />
        <PackageReference Include="NSwag.AspNetCore" Version="${nswagVersion}" />
        <PackageReference Include="Serilog.AspNetCore" Version="${serilogVersion}" />
        <PackageReference Include="Serilog.Enrichers.Environment" Version="${enrichmentEnvVersion}" />
        <PackageReference Include="Serilog.Enrichers.Thread" Version="${enrichmentThreadVersion}" />
    </ItemGroup>
</Project>

Replace ${authVersion}, ${jwtVersion}, ${nswagVersion}, ${serilogVersion}, ${enrichmentEnvVersion}, and ${enrichmentThreadVersion} with your respective NuGet package versions.

The benefits of these changes include:

• Easier dependency management
• Improved maintainability
• Better readability

These are general best practices for improving C# project files. Remember to consider the specific requirements of your project and adjust them accordingly.