search

HavenDV / Uno.Sdk

Single project solution for Uno
Other
7 stars 0 forks source link

build(deps): Bump the all group across 1 directory with 5 updates #54

Open dependabot[bot] opened 3 months ago

dependabot[bot] commented 3 months ago

Bumps the all group with 5 updates in the / directory:

Package From To
Microsoft.NET.Test.Sdk 17.8.0 17.10.0
MSTest.TestAdapter 3.1.1 3.4.3
MSTest.TestFramework 3.1.1 3.4.3
WixSharp 1.22.1 1.25.3
WixSharp.wix.bin 3.14.0 3.14.1

Updates Microsoft.NET.Test.Sdk from 17.8.0 to 17.10.0

Release notes

Sourced from Microsoft.NET.Test.Sdk's releases.

v17.10.0

What's Changed

And many infrastructure related changes and updates.

New Contributors

Full Changelog: https://github.com/microsoft/vstest/compare/v17.9.0...v17.10.0

v17.10.0-release-24177-07

What's Changed

... (truncated)

Commits


Updates MSTest.TestAdapter from 3.1.1 to 3.4.3

Release notes

Sourced from MSTest.TestAdapter's releases.

v3.4.3

See the release notes here

v.3.4.2

See the release notes here

v3.4.1

See the release notes here

v3.4.0

Here are the highlights of the current release, full change log is available below:

https://github.com/microsoft/testfx/compare/v3.3.1...v3.4.0

MSTest

New and improved analyzers

We've added more code analyzers to help you prevent mistakes, and to ensure a consistent code style of your tests.

One example of a new analyzer that was added in 3.4.0 is MSTEST0024: Do not store TestContext in static members. This analyzer has info severity by default, and will show a message, when you store TestContext in a static member in your class. This is not recommended, and you should be using a TestContext property instead:

image

The other analyzers added in this release:

If you've just learned about MSTest analyzers, please also check out the analyzers that were added in previous releases. They will help you ensure that your test classes and test methods are recognized by MSTest and are not accidentally ignored.

The analyzers are automatically installed with the MSTest NuGet meta-package. But can also be installed separately using the MSTest.Analyzers NuGet package.

More timeout options

Timeout can now be specified on all fixture methods, including ClassCleanup, AssemblyCleanup, TestCleanup and TestInitalize. In this case I want my [ClassCleanup] to time out after 1 second:

image

Alternatively timeouts can be specified through runsettings. For example like this:

<RunSettings>
  <MSTest>
</tr></table>

... (truncated)

Changelog

Sourced from MSTest.TestAdapter's changelog.

[3.4.3] - 2024-05-30

See full log here

Fixed

Artifacts

  • MSTest: 3.4.3
  • MSTest.TestFramework: 3.4.3
  • MSTest.TestAdapter: 3.4.3
  • MSTest.Analyzers: 3.4.3
  • MSTest.Sdk: 3.4.3
  • Microsoft.Testing.Extensions.CrashDump: 1.2.1
  • Microsoft.Testing.Extensions.HangDump: 1.2.1
  • Microsoft.Testing.Extensions.HotReload: 1.2.1
  • Microsoft.Testing.Extensions.Retry: 1.2.1
  • Microsoft.Testing.Extensions.TrxReport: 1.2.1

[3.4.2] - 2024-05-30

See full log here

Fixed

Artifacts

  • MSTest: 3.4.2
  • MSTest.TestFramework: 3.4.2
  • MSTest.TestAdapter: 3.4.2
  • MSTest.Analyzers: 3.4.2
  • MSTest.Sdk: 3.4.2
  • Microsoft.Testing.Extensions.CrashDump: 1.2.1
  • Microsoft.Testing.Extensions.HangDump: 1.2.1
  • Microsoft.Testing.Extensions.HotReload: 1.2.1
  • Microsoft.Testing.Extensions.Retry: 1.2.1
  • Microsoft.Testing.Extensions.TrxReport: 1.2.1

[3.4.1] - 2024-05-27

See full log here

Fixed

... (truncated)

Commits


Updates MSTest.TestFramework from 3.1.1 to 3.4.3

Release notes

Sourced from MSTest.TestFramework's releases.

v3.4.3

See the release notes here

v.3.4.2

See the release notes here

v3.4.1

See the release notes here

v3.4.0

Here are the highlights of the current release, full change log is available below:

https://github.com/microsoft/testfx/compare/v3.3.1...v3.4.0

MSTest

New and improved analyzers

We've added more code analyzers to help you prevent mistakes, and to ensure a consistent code style of your tests.

One example of a new analyzer that was added in 3.4.0 is MSTEST0024: Do not store TestContext in static members. This analyzer has info severity by default, and will show a message, when you store TestContext in a static member in your class. This is not recommended, and you should be using a TestContext property instead:

image

The other analyzers added in this release:

If you've just learned about MSTest analyzers, please also check out the analyzers that were added in previous releases. They will help you ensure that your test classes and test methods are recognized by MSTest and are not accidentally ignored.

The analyzers are automatically installed with the MSTest NuGet meta-package. But can also be installed separately using the MSTest.Analyzers NuGet package.

More timeout options

Timeout can now be specified on all fixture methods, including ClassCleanup, AssemblyCleanup, TestCleanup and TestInitalize. In this case I want my [ClassCleanup] to time out after 1 second:

image

Alternatively timeouts can be specified through runsettings. For example like this:

<RunSettings>
  <MSTest>
</tr></table>

... (truncated)

Changelog

Sourced from MSTest.TestFramework's changelog.

[3.4.3] - 2024-05-30

See full log here

Fixed

Artifacts

  • MSTest: 3.4.3
  • MSTest.TestFramework: 3.4.3
  • MSTest.TestAdapter: 3.4.3
  • MSTest.Analyzers: 3.4.3
  • MSTest.Sdk: 3.4.3
  • Microsoft.Testing.Extensions.CrashDump: 1.2.1
  • Microsoft.Testing.Extensions.HangDump: 1.2.1
  • Microsoft.Testing.Extensions.HotReload: 1.2.1
  • Microsoft.Testing.Extensions.Retry: 1.2.1
  • Microsoft.Testing.Extensions.TrxReport: 1.2.1

[3.4.2] - 2024-05-30

See full log here

Fixed

Artifacts

  • MSTest: 3.4.2
  • MSTest.TestFramework: 3.4.2
  • MSTest.TestAdapter: 3.4.2
  • MSTest.Analyzers: 3.4.2
  • MSTest.Sdk: 3.4.2
  • Microsoft.Testing.Extensions.CrashDump: 1.2.1
  • Microsoft.Testing.Extensions.HangDump: 1.2.1
  • Microsoft.Testing.Extensions.HotReload: 1.2.1
  • Microsoft.Testing.Extensions.Retry: 1.2.1
  • Microsoft.Testing.Extensions.TrxReport: 1.2.1

[3.4.1] - 2024-05-27

See full log here

Fixed

... (truncated)

Commits


Updates WixSharp from 1.22.1 to 1.25.3

Release notes

Sourced from WixSharp's releases.

WiX4: Release v2.1.4.0 (.NET Core only)

  • Issue #1444: wix.exe not found if installed as local tool

WiX3: Release v1.25.3.0

Special thanks to @​geghamyan for contributing Project.SignAllFiles functionality.

NOTE, Project.SignAllFiles=false by default but it will be changed to Project.SignAllFiles=true in the next release.

  • Added file signing functionality to project build process (Project.SignAllFiles).
  • fixed an accidental recursion in AsWixVarToPath
  • Issue #1490: Missing images in Managed WPF UI
  • Updated WixSharp.wix.bin.3.14.1.nupkg

WiX3-Release v1.25.2.0

  • #1464: Installer crashes when using custom UIs with Features
  • #1460: Add -sw1026 to default Wix4 argument options?
  • #1459: ShortCut Icon Tooltip
  • #1406: Multi-language improvement
  • Added ManagedAction for CA implemented as native DLLs (e.g. AOT assemblies). Triggered by proposal #1456

WiX3-Release v1.25.1.0

(repeat of v1.25.0.0 nuget release because of the packaging problem)

  • #1446: Catch all exceptions in managed WinForms UI
  • Added sample for #1449
  • #1421 Update Text (Dialog title) on view title change (@​PatrickHofman)
  • Proposal #1263: Signing using JSign or other alternatives

WiX3-Release v1.24.2.0

  • WiX3: improvements triggered by #1424
  • Feature condition support in managed UI #1430
  • Added support for condition evaluation and custom installlevel settings.
  • Issue #1405: Can't make LookupInstalledVersion work
  • added test case for Issue #1403
  • updated the WPF BA sample to show the solution for #1400
  • Enhancement #1401: Can't mark directory as permanent

WiX3-Release v1.24.1.0

SHA-1: dc5717d2a19f8ff12d5dd06f659aab473ef54d46

  • #1363: Shortcut to Dir/Folder
  • #1398: Underscore in String Id in wxl breaks localization
  • reverted experimental change for x86 bitness of WixSharp.UI. Now it's back to AnyCPU but SilentUI BA will no longer work. It's acceptable as it's better to set x86 on the user codebase (e.g. custom BA) than on generic lib (WixSharp.UI) and put bitness pressure on all users of this lib.
  • WarnOnOutputPathCollision changed from Warning to Error (continuation of #1384).
  • Extended cascading Project.Platform to RegistrySearch (triggered by #1390 discussion).

WiX3-Release v1.24.0.0

v1.24.0.0

  • Issue #1392: Is it possible to inherit wxl files using managed UI?
  • Issue #1389: Multi language installer intermediate .msi not found error
  • Issue #1387: Cannot update to latest Caliburn.Micro

... (truncated)

Commits


Updates WixSharp.wix.bin from 3.14.0 to 3.14.1

Release notes

Sourced from WixSharp.wix.bin's releases.

WiX4: Release v2.1.4.0 (.NET Core only)

  • Issue #1444: wix.exe not found if installed as local tool

Release v1.4.1.0 (HotFix)

  • Issue #27: Fixing AppSearch.GetProducts() crash
  • Added support for MediaTemplate element.
  • Added tunneling of Files and DirFiles attributes to the aggregated File items
  • Issue #23: Attributes inheritance in Files and DirFiles
  • Added Compiler.GetMappedWixConstants() for exploring WiX constants mapping
  • Adding %CommonAppDataFolder% to Dir.cs description
  • Issue #20: File.Attributes (on parent Component) after setting File.NeverOverwrite will not work
Commits


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 merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore major version` will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) - `@dependabot ignore minor version` will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) - `@dependabot ignore ` will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) - `@dependabot unignore ` will remove all of the ignore conditions of the specified dependency - `@dependabot unignore ` will remove the ignore condition of the specified dependency and ignore conditions