Bump BenchmarkDotNet and 5 others #58
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updated BenchmarkDotNet from 0.14.0 to 0.15.2.
Release notes
Sourced from BenchmarkDotNet's releases.
0.15.2
Full changelog: https://benchmarkdotnet.org/changelog/v0.15.2.html
Highlights
0.15.1
Full changelog: https://benchmarkdotnet.org/changelog/v0.15.1.html
Highlights
0.15.0
Full changelog: https://benchmarkdotnet.org/changelog/v0.15.0.html
Commits viewable in compare view.
Updated Microsoft.NET.Test.Sdk from 17.13.0 to 17.14.1.
Release notes
Sourced from Microsoft.NET.Test.Sdk's releases.
17.14.1
What's Changed
Full Changelog: microsoft/vstest@v17.14.0...v17.14.1
17.14.0
What's Changed
.NET versions updated
This version of VS Test upgraded .NET to net8 and net9. All projects targeting net6.0 (or other end-of-life .NET target frameworks) should pin their version of Microsoft.NET.Test.SDK to 17.13.0, or update the projects to net8 or newer. We remain backwards compatible with previous versions of Microsoft.NET.Test.SDK. This change does NOT prevent you from:
It also has no impact on .NET Framework projects, where we continue targeting .NET Framework 4.6.2.
Changes
Internal version updates and fixes
New Contributors
... (truncated)
17.14.0-preview-25107-01
What's Changed
.NET versions updated
This version of VS Test upgraded .NET to net8 and net9. All projects targeting net6.0 (or other end-of-life .NET target frameworks) should pin their version of Microsoft.NET.Test.SDK to 17.13.0, or update the projects to net8 or newer. We remain backwards compatible with previous versions of Microsoft.NET.Test.SDK. This change does NOT prevent you from:
It also has no impact on .NET Framework projects, where we continue targeting .NET Framework 4.6.2.
Changes
Internal version updates and fixes
Will probably revert before release:
New Contributors
Full Changelog: microsoft/vstest@v17.13.0...v17.14.0-preview-25107-01
Commits viewable in compare view.
Updated PuppeteerSharp from 18.1.0 to 20.2.2.
Release notes
Sourced from PuppeteerSharp's releases.
20.2.2
What's Changed
Full Changelog: hardkoded/puppeteer-sharp@v20.2.1...v20.2.2
20.2.1
What's Changed
New Contributors
Full Changelog: hardkoded/puppeteer-sharp@v20.2.0...v20.2.1
20.2.0
What's new
What's Changed
Full Changelog: hardkoded/puppeteer-sharp@v20.1.3...v20.2.0
20.1.3
What's Changed
Full Changelog: hardkoded/puppeteer-sharp@v20.1.2...v20.1.3
20.1.2
What's Changed
Full Changelog: hardkoded/puppeteer-sharp@v20.1.1...v20.1.2
20.1.1
What's Changed
Full Changelog: hardkoded/puppeteer-sharp@v20.1.0...v20.1.1
20.1.0
What's new
What's Changed
Full Changelog: hardkoded/puppeteer-sharp@v20.0.5...v20.1.0
20.0.5
What's Changed
Full Changelog: hardkoded/puppeteer-sharp@v20.0.4...v20.0.5
20.0.4
What's new
What's Changed
New Contributors
Full Changelog: hardkoded/puppeteer-sharp@v20.0.3...v20.0.4
20.0.3
What's New
What's Changed
New Contributors
Full Changelog: hardkoded/puppeteer-sharp@v20.0.2...v20.0.3
20.0.2
What's Changed
New Contributors
Full Changelog: hardkoded/puppeteer-sharp@v20.0.0...v20.0.2
20.0.0
Breaking changes
There are, technically speaking, some breaking changes. I hope it's not a big deal for you.
Use byte array in message send
By @campersau in hardkoded/puppeteer-sharp#2749
If you implemented a custom
IConnectionTransport
. The new signature ofSendAsync
isTask SendAsync(byte[] message);
IRequest.PostData is now a string
This matches the type in Puppeteer.
What's new
What's Changed
Full Changelog: hardkoded/puppeteer-sharp@v19.0.2...v20.0.0
19.0.2
What's Changed
Full Changelog: hardkoded/puppeteer-sharp@v19.0.1...v19.0.2
19.0.1
What's Changed
Full Changelog: hardkoded/puppeteer-sharp@v19.0.0...v19.0.1
19.0.0
Welcome System.Text.Json and AOT support!
What's new
Full AOT Support.
v19 comes with one of the most significant changes made to this library. We are moving away from Newtonsoft JSON in favor of System.Text.Json. The motivation behind this change is that it would get us closer to AOT support.
If you are using your own classes to interact with the browser through
EvaluateFunctionAsync
or similar, you will have to provide your ownJsonSerializerContext
to puppeteer using the staticPuppeteer.ExtraJsonSerializerContext
property.For instance.
The serializer would look like this:
For more information about
JsonSerializerContext
see How to use source generation in System.Text.Json.Breaking changes
JSON is critical for PuppeteerSharp. It's how we communicate with the browser, so changing the library used to perform this communication is quite risky.
Newtonsoft JSON classes were also used in our API, so your code might have some breaking changes.
Newtonsoft's
JToken
was replaced withJsonElement
JToken
was the default type for functions likeEvaluationFunctionAsync
,EvaluateExpressionAsync
orJsonAsync
, when the generic function was not used.Before: