Bump versions using new (coherent) darc tool

[dougbu]

No description provided.

[natemcmaster]

Why has this been added only for this dependency and not all dependencies from aspnet/Extensions?

[dougbu]

I didn't bother to update the ... .Sources dependencies.

[dougbu]

FYI, despite our questions, the CI checks were successful.

[NTaylorMullen]

What does having a CoherentParentDependency do? If the parent dependency changes the child gets it's version updated too?

[dougbu]

What does having a CoherentParentDependency do?

It informs a new version of the darc tool that it should ensure the chosen dependencies all have a common transitive dependency. In this case, we're ensuring every dependency (except .Sources packages and tools) shares their Microsoft.NETCore.App versions.

[NTaylorMullen]

It informs a new version of the darc tool that it should ensure the chosen dependencies all have a common transitive dependency. In this case, we're ensuring every dependency (except .Sources packages and tools) shares their Microsoft.NETCore.App versions.

Ahhh gotcha, enforcing coherence 👍

[ryanbrandenburg]

LGTM. Does darc add "CoherentParentDependency" items for us or do we have to do it manually?

[dougbu]

Does darc add "CoherentParentDependency" items for us or do we have to do it manually?

We do it manually. Once this is all in, the docs/ReferenceResolution.md doc in Extensions and AspNetCore to include the attribute in the "adding a new dependency" blurb.

BTW I'm not merging this because I used the wrong syntax.

[dougbu]

Closing this. I'm going to redo this using the correct syntax and whatever @mmitche comes up with for our second diamond dependencies (w/ Extensions).