Bump the dev-dependencies group with 3 updates#46
Closed
dependabot[bot] wants to merge 1 commit intomainfrom
Closed
Bump the dev-dependencies group with 3 updates#46dependabot[bot] wants to merge 1 commit intomainfrom
dependabot[bot] wants to merge 1 commit intomainfrom
Conversation
Bumps AsmResolver.DotNet from 6.0.0-beta.5 to 6.0.0-beta.6 Bumps docfx from 2.78.4 to 2.78.5 Bumps Microsoft.NET.Test.Sdk from 18.0.1 to 18.3.0 --- updated-dependencies: - dependency-name: docfx dependency-version: 2.78.5 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: dev-dependencies - dependency-name: docfx dependency-version: 2.78.5 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: dev-dependencies - dependency-name: Microsoft.NET.Test.Sdk dependency-version: 18.3.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: dev-dependencies - dependency-name: AsmResolver.DotNet dependency-version: 6.0.0-beta.6 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: dev-dependencies - dependency-name: docfx dependency-version: 2.78.5 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: dev-dependencies - dependency-name: Microsoft.NET.Test.Sdk dependency-version: 18.3.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: dev-dependencies ... Signed-off-by: dependabot[bot] <support@github.com>
Author
|
Looks like these dependencies are updatable in another way, so this is no longer needed. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 AsmResolver.DotNet from 6.0.0-beta.5 to 6.0.0-beta.6.
Release notes
Sourced from AsmResolver.DotNet's releases.
6.0.0-beta.6
This release brings the long-needed metadata resolution revamp. The previous system often caused incorrect, duplicated, or silent failed assembly resolutions, which sometimes resulted in bad metadata to be emitted in output binaries. The new system makes
RuntimeContextact more like anAppDomain/AssemblyLoadContext, centralizing assembly management and requiring all metadata resolution to go through it. Resolution is now also much more explicit, by always requiring aRuntimeContextinstance. This ensures more reliable, predictable behavior when creating and processing .NET metadata.Check out the updated documentation on RuntimeContexts on how to use the new APIs.
Full change log below:
New Features
RuntimeContexts (#704).IAssemblyResolveris drastically simplified and is no longer responsible for caching anymore.IMetadataResolverand friends are removed.RuntimeContextconstruction is drastically simplified.RuntimeContextis now responsible for resolving and maintaining assembly and metadata caches.RuntimeContext::LoadAssemblymethods to load assemblies into the context (similar toAssemblyDefinition::FromX, but using the context for reader parameters, cache and automatic wiring of dependencies).Resolvemethods in favor of aResolveandTryResolvemethod taking aRuntimeContext. Additionally, all properties and methods that may have implicitly required resolution will now take aRuntimeContextas well.SignatureComparercan now take aRuntimeContextin its constructor. When none is provided, the comparer will no longer try to resolve forwarder types and compare signatures as-is.TargetRuntimeProberto detect the target runtime of a PE image without loading it as a fullModuleDefinition(#704).MetadataDirectory::GetImpliedStreamSelection()(#704).S_TRAMPOLINEandS_GTHREAD32andS_LTHREAD32PDB symbols (#711, thanks @dongle-the-gadget).Improvements
UnmanagedPEFileBuildertoTemplatedPEFileBuilderto more accurately reflect its behavior (727c554571a848f2e09a1d7aa4365c287bd90934)KnownCorLibs) (#702, 55c847fd7617755ef09fffdf3512d454151bc7df).BinaryStreamWriterfor .NET 10+ targets (#695, thanks @Sergio0694).Utf8StringimplementISpanFormattableandIUtf8SpanFormattable(#699, thanks @Sergio0694).Utf8String::CreateUnsafefactory method (#709, thanks @Windows10CE)TypeAttributes::WindowsRuntime(#710, thanks @Sergio0694).ModuleDefinition::CreateConstructoroverload takingCorLibTypeFactory(#712, thanks @Sergio0694).Class2,Structure2,Union2andInterface2PDB leaf record types (#714, thanks @ds5678).Bug Fixes
Commits viewable in compare view.
Updated docfx from 2.78.4 to 2.78.5.
Release notes
Sourced from docfx's releases.
2.78.5
What's Changed
Add support for .NET 10 target framework by @filzrev in dotnet/docfx#10859
Full Changelog: dotnet/docfx@v2.78.4...v2.78.5
Commits viewable in compare view.
Updated Microsoft.NET.Test.Sdk from 18.0.1 to 18.3.0.
Release notes
Sourced from Microsoft.NET.Test.Sdk's releases.
18.3.0
What's Changed
Internal fixes and updates
New Contributors
Commits viewable in compare view.
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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill 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 <dependency name> minor versionwill 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 <dependency name>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 <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions