Bump Microsoft.AspNetCore.Authentication.JwtBearer from 8.0.27 to 8.0.28

[dependabot]

Updated Microsoft.AspNetCore.Authentication.JwtBearer from 8.0.27 to 8.0.28.

Release notes

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

8.0.28

Release

What's Changed

• Update branding to 8.0.28 by @​vseanreesermsft in Update branding to 8.0.28 dotnet/aspnetcore#66589
• [release/8.0] Update dependencies from dotnet/arcade by @​dotnet-maestro[bot] in [release/8.0] Update dependencies from dotnet/arcade dotnet/aspnetcore#66556
• [release/8.0] Update dependencies from dotnet/source-build-assets by @​dotnet-maestro[bot] in [release/8.0] Update dependencies from dotnet/source-build-assets dotnet/aspnetcore#66471
• [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#66344
• [release/8.0] Strip UTF-8 BOM from template localization files and remove version override by @​wtgodbe in [release/8.0] Strip UTF-8 BOM from template localization files and remove version override dotnet/aspnetcore#66427
• Merging internal commits for release/8.0 by @​vseanreesermsft in Merging internal commits for release/8.0 dotnet/aspnetcore#66662

Full Changelog: dotnet/aspnetcore@v8.0.27...v8.0.28

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\nCode Review and Suggestions

The provided code snippet is a C# project file (.csproj) for a web application using the .NET SDK. Here are some suggestions for improvement, coding best practices, readability, and maintainability:

1. Use meaningful variable names

Instead of hardcoding values in the PropertyGroup section, consider defining them as constants or using a configuration file.

<Project Sdk="Microsoft.NET.Sdk.Web">
    <PropertyGroup>
        <!-- Define target framework as a constant -->
        <TargetFramework>net8.0</TargetFramework>

        <!-- Use a configuration file for secrets -->
        <UserSecretsId>${UserSecrets:9d750d08-73ae-4876-83cc-4aad393eef18}</UserSecretsId>

        <!-- Define default target OS as a constant -->
        <DockerDefaultTargetOS>Linux</DockerDefaultTargetOS>
    </PropertyGroup>
    ...
</Project>

2. Organize Package References

Instead of listing all package references in a single ItemGroup, consider grouping them by category (e.g., authentication, logging, etc.) for better readability and maintainability.

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

    <!-- Authentication packages -->
    <ItemGroup>
        <PackageReference Include="Microsoft.AspNetCore.Authentication" Version="2.3.10" />
        <PackageReference Include="Microsoft.AspNetCore.Authentication.JwtBearer" Version="8.0.28" />
    </ItemGroup>

    <!-- Logging packages -->
    <ItemGroup>
        <PackageReference Include="NSwag.AspNetCore" Version="14.7.1" />
        <PackageReference Include="Serilog.AspNetCore" Version="10.0.0" />
        <PackageReference Include="Serilog.Enrichers.Environment" Version="3.0.1" />
        <PackageReference Include="Serilog.Enrichers.Thread" Version="4.0.0" />
    </ItemGroup>
</Project>

3. Use XML comments for packages

Consider adding XML comments to package references to provide a brief description of the package.

<ItemGroup>
    <PackageReference Include="Microsoft.AspNetCore.Authentication" Version="2.3.10">
        <!-- Add a brief description -->
        <Description>ASP.NET Core authentication library</Description>
    </PackageReference>

    <!-- ... -->
</ItemGroup>

4. Consider using a configuration file

Instead of hardcoding values in the PropertyGroup section, consider using a configuration file (e.g., appsettings.json) to store sensitive information like secrets.

{
    "UserSecretsId": "9d750d08-73ae-4876-83cc-4aad393eef18"
}

5. Use semantic versioning for package references

Consider using semantic versioning (e.g., Microsoft.AspNetCore.Authentication >= 2.3.10) to ensure compatibility with the latest package versions.

<ItemGroup>
    <PackageReference Include="Microsoft.AspNetCore.Authentication" Version=">=2.3.10" />
    <!-- ... -->
</ItemGroup>

By applying these suggestions, you can improve the readability, maintainability, and overall quality of your project file.