Skip to content

Conversation

@ViktorHofer
Copy link
Member

Fixes #48248
Fixes #48306
Fixes #48307

@ghost
Copy link

ghost commented Feb 15, 2021

Tagging subscribers to this area: @eerhardt, @maryamariyan
See info in area-owners.md if you want to be subscribed.

Issue Details

Fixes #48248
Fixes #48306
Fixes #48307

Author: ViktorHofer
Assignees: ViktorHofer
Labels:

area-Extensions-DependencyInjection

Milestone: -

@ghost
Copy link

ghost commented Feb 16, 2021

Tagging subscribers to this area: @safern, @ViktorHofer
See info in area-owners.md if you want to be subscribed.

Issue Details

Fixes #48248
Fixes #48306
Fixes #48307

Author: ViktorHofer
Assignees: ViktorHofer
Labels:

area-Extensions-DependencyInjection, area-Infrastructure-libraries

Milestone: -

Copy link
Member

@safern safern left a comment

Choose a reason for hiding this comment

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

LGTM

@ViktorHofer
Copy link
Member Author

@maryamariyan I don't think this is an infra issue per-se but I'm ok with using that label for the sake of just having a single area.

@ViktorHofer
Copy link
Member Author

I talked with @ericstj about this offline and dropping a tfm that already shipped isn't considered a breaking change as long as the nearest compatible asset that is picked up instead isn't noticeably different (ie AssemblyVersion).

Based on that I dropped the net5.0 asset in Microsoft.Extensions.DependencyInjection which unintentionally shipped and downgraded the net5.0 asset in Microsoft.Extensions.Options to netcoreapp3.1 which was the tfm previously shipped before the project was migrated to dotnet/runtime. Spoke with @maryamariyan about this offline as well.

Copy link
Member

@joperezr joperezr left a comment

Choose a reason for hiding this comment

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

LGTM thanks for fixing

@maryamariyan
Copy link
Contributor

@maryamariyan I don't think this is an infra issue per-se but I'm ok with using that label for the sake of just having a single area.

I was debating between area-Meta (because of multiple projects and it fixing different issues), area-Infra* (because of PR title), or just keeping DI (diff mostly in DI). Sure I'll move back,

@ghost
Copy link

ghost commented Feb 17, 2021

Tagging subscribers to this area: @eerhardt, @maryamariyan
See info in area-owners.md if you want to be subscribed.

Issue Details

Fixes #48248
Fixes #48306
Fixes #48307

Author: ViktorHofer
Assignees: ViktorHofer
Labels:

area-Extensions-DependencyInjection, area-Infrastructure-libraries

Milestone: -

Copy link
Member

@eerhardt eerhardt left a comment

Choose a reason for hiding this comment

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

LGTM. Thanks for making these projects better while you were here, @ViktorHofer!

@ViktorHofer
Copy link
Member Author

Failure is #30056

@ViktorHofer ViktorHofer merged commit 225b700 into dotnet:master Feb 18, 2021
@ViktorHofer ViktorHofer deleted the FixPkgConfigurations branch February 18, 2021 14:38
@ghost ghost locked as resolved and limited conversation to collaborators Mar 20, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

8 participants