chore(deps): update dependency microsoft.net.test.sdk to 18.3.0

[renovate-bot]

This PR contains the following updates:

Package	Change	Age	Confidence
Microsoft.NET.Test.Sdk	18.0.1 → 18.3.0

---

Release Notes

microsoft/vstest (Microsoft.NET.Test.Sdk)

v18.3.0

What's Changed

• Fix answer file splitting by @​nohwnd in #​15306

Internal fixes and updates

• Bump branding to 18.1 by @​nohwnd in #​15286
• Remove stale copy of S.ComponentModel.Composition from testplatform packages by @​ViktorHofer in #​15287
• Update codeflow metadata to fix backflow by @​premun in #​15291
• [main] Update dependencies from devdiv/DevDiv/vs-code-coverage by @​dotnet-maestro[bot] in #​15283
• Update Microsoft.Build.Utilities.Core by @​Youssef1313 in #​15300
• Disable DynamicNative instrumentation by default by @​nohwnd in #​15299
• [main] Source code updates from dotnet/dotnet by @​dotnet-maestro[bot] in #​15293
• [main] Source code updates from dotnet/dotnet by @​dotnet-maestro[bot] in #​15302
• [main] Source code updates from dotnet/dotnet by @​dotnet-maestro[bot] in #​15314
• Delete sha1 custom implementation we are not using for a long time by @​nohwnd in #​15313
• [main] Source code updates from dotnet/dotnet by @​dotnet-maestro[bot] in #​15315
• Update branding to 18.3.0 by @​nohwnd in #​15321
• [main] Update dependencies from devdiv/DevDiv/vs-code-coverage by @​dotnet-maestro[bot] in #​15325
• [main] Update dependencies from dotnet/arcade by @​dotnet-maestro[bot] in #​15264
• Revert adding dotnet_host_path workaround by @​nohwnd in #​15328
• [main] Update dependencies from dotnet/arcade by @​dotnet-maestro[bot] in #​15338
• [main] Source code updates from dotnet/dotnet by @​dotnet-maestro[bot] in #​15322
• [main] Update dependencies from dotnet/arcade by @​dotnet-maestro[bot] in #​15343
• Change PreReleaseVersionLabel from 'preview' to 'release' by @​nohwnd in #​15352
• [rel/18.3] Update dependencies from devdiv/DevDiv/vs-code-coverage by @​dotnet-maestro[bot] in #​15354
• [rel/18.3] Update dependencies from dotnet/arcade by @​dotnet-maestro[bot] in #​15389
• [rel/18.3] Update dependencies from dotnet/arcade by @​dotnet-maestro[bot] in #​15400
• Update build tools to 17.11.48 to be source buildable by @​nohwnd in #​15310
• Disable publishing on RTM by @​nohwnd in #​15296
• Don't access nuget.org for package feeds by @​nohwnd in #​15316
• No nuget access fix tests by @​nohwnd in #​15317
• Disable Dependabot updates in dependabot.yml by @​mmitche in #​15324

New Contributors

• @​premun made their first contribution in #​15291

---

Configuration

📅 Schedule: Branch creation - "before 8am" in timezone Europe/London, 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.

[gemini-code-assist]

Summary of Changes

Hello @renovate-bot, I'm Gemini Code Assist¹! 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 updates the Microsoft.NET.Test.Sdk dependency to its latest version, 18.3.0. This ensures the project benefits from the latest test SDK features, bug fixes, and performance improvements, maintaining compatibility and leveraging updated testing capabilities.

Highlights

• Dependency Update: Updated the Microsoft.NET.Test.Sdk dependency from version 18.0.1 to 18.3.0.

Changelog

• Directory.Packages.props
  • Updated the Microsoft.NET.Test.Sdk package version from 18.0.1 to 18.3.0.

Activity

• This pull request was automatically generated by Renovate Bot.
• Automerge is currently disabled, 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. ↩

[gemini-code-assist]

Code Review

This pull request contains an automated dependency update for Microsoft.NET.Test.Sdk, from version 18.0.1 to 18.3.0. The change is correctly applied in Directory.Packages.props. Based on the release notes, this is a minor update with bug fixes and internal improvements, and no breaking changes are indicated. The update appears to be safe and ready for merging.