Skip to content

chore: update dependency nunit to 4.5.1#713

Open
renovate-bot wants to merge 1 commit intogoogleapis:mainfrom
renovate-bot:renovate/nunit-4.x
Open

chore: update dependency nunit to 4.5.1#713
renovate-bot wants to merge 1 commit intogoogleapis:mainfrom
renovate-bot:renovate/nunit-4.x

Conversation

@renovate-bot
Copy link
Contributor

This PR contains the following updates:

Package Change Age Confidence
NUnit (source) 4.5.04.5.1 age confidence

Release Notes

nunit/nunit (NUnit)

v4.5.1: V 4.5.1

Compare Source

See release notes for details.


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate-bot renovate-bot requested review from a team as code owners March 6, 2026 16:43
@trusted-contributions-gcf trusted-contributions-gcf bot added the kokoro:force-run Add this label to force Kokoro to re-run the tests. label Mar 6, 2026
@gemini-code-assist
Copy link

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request performs a minor version update for the NUnit testing framework across two project files. This update ensures that the projects benefit from the latest bug fixes and minor improvements in the NUnit library, maintaining compatibility and stability for the test suites.

Highlights

  • Dependency Update: Updated the NUnit testing framework from version 4.5.0 to 4.5.1 in two project files.
Changelog
  • spanner-ado-net/spanner-ado-net-samples-tests/spanner-ado-net-samples-tests.csproj
    • Updated NUnit package reference from 4.5.0 to 4.5.1.
  • spanner-ado-net/spanner-ado-net-tests/spanner-ado-net-tests.csproj
    • Updated NUnit package reference from 4.5.0 to 4.5.1.
Activity
  • The pull request was automatically generated by renovate-bot.
  • Automerge is disabled by configuration, requiring manual merging.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This PR updates the NUnit dependency to version 4.5.1. The update is a minor patch and appears correct. I've added comments to both project files suggesting a future improvement: migrating from NUnit3TestAdapter to NUnit.TestAdapter. The latter is the recommended test adapter for NUnit 4+ and would ensure better compatibility and feature support for your test projects.

</PackageReference>
<PackageReference Include="Microsoft.NET.Test.Sdk" Version="18.3.0"/>
<PackageReference Include="NUnit" Version="4.5.0"/>
<PackageReference Include="NUnit" Version="4.5.1"/>

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

For NUnit 4 and higher, the recommended test adapter is NUnit.TestAdapter. This project is currently using NUnit3TestAdapter, which is primarily intended for NUnit 3.x. While it has compatibility with NUnit 4, migrating to NUnit.TestAdapter is advisable for better integration and to leverage all features of the NUnit 4 framework.

This would be a separate change, but you might consider replacing NUnit3TestAdapter with NUnit.TestAdapter (the latest version is 4.5.0) to align the testing setup with NUnit 4 best practices.

</PackageReference>
<PackageReference Include="Microsoft.NET.Test.Sdk" Version="18.3.0"/>
<PackageReference Include="NUnit" Version="4.5.0"/>
<PackageReference Include="NUnit" Version="4.5.1"/>

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

For NUnit 4 and higher, the recommended test adapter is NUnit.TestAdapter. This project is currently using NUnit3TestAdapter, which is primarily intended for NUnit 3.x. While it has compatibility with NUnit 4, migrating to NUnit.TestAdapter is advisable for better integration and to leverage all features of the NUnit 4 framework.

This would be a separate change, but you might consider replacing NUnit3TestAdapter with NUnit.TestAdapter (the latest version is 4.5.0) to align the testing setup with NUnit 4 best practices.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

kokoro:force-run Add this label to force Kokoro to re-run the tests.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant