chore(ci): update config for Dependabot lock file handling

[nanotaboada]

Summary by CodeRabbit

• New Features

  • Enabled enhanced caching during builds to improve the efficiency of dependency handling.

• Chores

  • Updated dependency management by aligning package versions and adjusting lock file usage for improved consistency and performance.

[coderabbitai]

Walkthrough

The changes update the .NET CI pipeline and project configurations. The GitHub Actions workflow now includes a new cache-dependency-path option to specify multiple dependency lock file paths. Both the Web API and test project files no longer reference the <NuGetLockFilePath> element. Additionally, a new packages.lock.json file has been added for the test project, and the main Web API lock file has been updated to upgrade several dependency versions from 9.0.2 to 9.0.3 with corresponding content hash updates.

Changes

File(s)	Change Summary
.github/workflows/dotnet.yml	Added cache-dependency-path to specify multiple dependency lock file paths for caching in the CI pipeline.
Dotnet.Samples.AspNetCore.WebApi/…csproj, Dotnet.Samples.AspNetCore.WebApi.Tests/…csproj	Removed <NuGetLockFilePath> element referencing ../packages.lock.json.
Dotnet.Samples.AspNetCore.WebApi.Tests/…/packages.lock.json	Added new lock file with dependency definitions for the test project.
Dotnet.Samples.AspNetCore.WebApi/…/packages.lock.json	Upgraded dependency versions from 9.0.2 to 9.0.3 and updated content hashes.

Sequence Diagram(s)

sequenceDiagram
    participant GH as GitHub Actions Workflow
    participant Setup as Set up .NET Step
    participant Cache as Caching System
    participant FS as File System

    GH->>Setup: Trigger CI workflow
    Setup->>Cache: Read cache-dependency-path property
    Cache->>FS: Locate specified dependency lock files
    FS-->>Cache: Return file status/details
    Cache-->>Setup: Provide cache hit/miss outcome
    Setup->>GH: Continue job execution

Loading

Suggested labels

dependencies, .NET

Tip

⚡🧪 Multi-step agentic review comment chat (experimental)

• We're introducing multi-step agentic chat in review comments. This experimental feature enhances review discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments.
  - To enable this feature, set early_access to true under in the settings.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 30e3fe1 and faa80b9.

📒 Files selected for processing (5)

• .github/workflows/dotnet.yml (1 hunks)
• Dotnet.Samples.AspNetCore.WebApi.Tests/Dotnet.Samples.AspNetCore.WebApi.Tests.csproj (0 hunks)
• Dotnet.Samples.AspNetCore.WebApi.Tests/packages.lock.json (1 hunks)
• Dotnet.Samples.AspNetCore.WebApi/Dotnet.Samples.AspNetCore.WebApi.csproj (0 hunks)
• Dotnet.Samples.AspNetCore.WebApi/packages.lock.json (8 hunks)

💤 Files with no reviewable changes (2)

• Dotnet.Samples.AspNetCore.WebApi.Tests/Dotnet.Samples.AspNetCore.WebApi.Tests.csproj
• Dotnet.Samples.AspNetCore.WebApi/Dotnet.Samples.AspNetCore.WebApi.csproj

🔇 Additional comments (5)

.github/workflows/dotnet.yml (1)

29-33: Enhance CI Cache Configuration with Multiple Dependency Files

The new addition using cache-dependency-path correctly lists both dependency lock files, which should help improve caching in the CI pipeline when dependency files are located in different subdirectories. Please verify that the specified paths are accurate relative to the repository root.

Dotnet.Samples.AspNetCore.WebApi.Tests/packages.lock.json (1)

1-1651: New Lock File for Test Project Added

This new packages.lock.json file comprehensively captures the dependency graph for the test project targeting net8.0. The file reflects updated dependency versions (e.g., upgrading several packages to version 9.0.3) and includes detailed fields such as requested, resolved, and contentHash for each dependency. It appears to be correctly generated, which will aid in consistent dependency restoration and better cache efficiency as configured in the workflow.

A couple of considerations:

• Ensure that this lock file is kept in sync with any future dependency updates.
• It might be useful to add brief documentation or a README note about the role of this lock file in your CI/CD process for team clarity.

Dotnet.Samples.AspNetCore.WebApi/packages.lock.json (3)

14-853: Comprehensive EF Core Dependency Updates
The changes in this large segment show that multiple EF Core–related packages (including Microsoft.EntityFrameworkCore.Design, InMemory, Sqlite, SqlServer and all related submodules like Core, Abstractions, Analyzers, Relational, and Sqlite.Core) have been uniformly bumped to version 9.0.3. The updated "requested", "resolved", and "contentHash" fields indicate that the package versions and their integrity checks now reflect the new release.

Please verify that these version bumps do not introduce any compatibility issues or breaking changes in the application. In particular, ensure that any downstream code using EF Core is tested against 9.0.3.

---

859-941: Microsoft.Extensions Libraries Update
Within this block, all the Microsoft.Extensions packages (such as Caching, Configuration, DependencyInjection, Logging, Options, and Primitives) are updated to version 9.0.3. This consistency helps ensure that the framework’s cross-cutting concerns (like dependency injection and caching) are aligned with the latest libraries.

It is advisable to confirm that these updates are reflected in the CI cache configuration (especially if you use Dependabot’s updated lock file settings) and that no version conflicts arise.

---

1410-1553: Core System Libraries Update
This section updates several core system libraries—specifically, System.Diagnostics.DiagnosticSource, System.Formats.Asn1, System.IO.Pipelines, System.Text.Encodings.Web, and System.Text.Json—to version 9.0.3. These updates are important for ensuring optimal performance, security, and compatibility in operations such as JSON serialization and data streaming.

Please double-check that these changes integrate smoothly with the rest of the dependency graph and that the application’s runtime behavior (e.g. serialization, pipeline processing) remains correct.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[codacy-production]

Coverage summary from Codacy

See diff coverage on Codacy

Coverage variation	Diff coverage
✅ +0.00%	✅ ∅

Coverage variation details

	Coverable lines	Covered lines	Coverage
Common ancestor commit (30e3fe1)	1225	697	56.90%
Head commit (faa80b9)	1225 (+0)	697 (+0)	56.90% (+0.00%)

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details

	Coverable lines	Covered lines	Diff coverage
Pull request (#181)	0	0	∅ (not applicable)

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

See your quality gate settings    Change summary preferences

_{Codacy stopped sending the deprecated coverage status on June 5th, 2024. Learn more}