Skip to content

[release/7.0.x] Source code updates from dotnet/dotnet#6925

Merged
dotnet-maestro[bot] merged 1 commit intorelease/7.0.xfrom
darc-release/7.0.x-f5b62dd2-f188-4e2e-99b2-58db2bee0e17
Nov 10, 2025
Merged

[release/7.0.x] Source code updates from dotnet/dotnet#6925
dotnet-maestro[bot] merged 1 commit intorelease/7.0.xfrom
darc-release/7.0.x-f5b62dd2-f188-4e2e-99b2-58db2bee0e17

Conversation

@dotnet-maestro
Copy link
Contributor

@dotnet-maestro dotnet-maestro bot commented Nov 10, 2025

Note

This is a codeflow update. It may contain both source code changes from
the VMR
as well as dependency updates. Learn more here.

This pull request brings the following source code changes

From https://github.com/dotnet/dotnet

Updated Dependencies

Associated changes in source repos

@dotnet-maestro
Update dependencies from https://github.com/dotnet/dotnet build 289695
3aebc8f 
Updated Dependencies:
Microsoft.DotNet.Arcade.Sdk, Microsoft.DotNet.XliffTasks (Version 10.0.0-beta.25531.102 -> 10.0.0-beta.25555.106)
@dotnet-maestro dotnet-maestro bot requested a review from a team as a code owner November 10, 2025 05:01
@dotnet-maestro dotnet-maestro bot requested review from jeffkl and nkolev92 November 10, 2025 05:01
@nkolev92
Copy link
Member

nkolev92 commented Nov 10, 2025

I wonder if we need to keep taking these and just keep producing new builds. I understand keeping dev up to date, but release/* doesn't seem necessary unless there's an actual change.

@NuGet/nuget-client looking for thoughts here.
It might be simpler to just keep accepting the changes, but we probably have freedom to ignore unnecessary branch updates.

@jeffkl
Copy link
Contributor

jeffkl commented Nov 10, 2025

I wonder if we need to keep taking these and just keep producing new builds. I understand keeping dev up to date, but release/* doesn't seem necessary unless there's an actual change.

@NuGet/nuget-client looking for thoughts here. It might be simpler to just keep accepting the changes, but we probably have freedom to ignore unnecessary branch updates.

I don't feel strongly one way or the other. I wonder if when we end up with more than 1 release branch if these updates will get overwhelming.

@dotnet-maestro dotnet-maestro bot merged commit fb44b97 into release/7.0.x Nov 10, 2025
22 checks passed
@dotnet-maestro dotnet-maestro bot deleted the darc-release/7.0.x-f5b62dd2-f188-4e2e-99b2-58db2bee0e17 branch November 10, 2025 22:56
@dotnet-maestro dotnet-maestro bot mentioned this pull request Dec 8, 2025
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@jeffkl jeffkl jeffkl approved these changes

@nkolev92 nkolev92 Awaiting requested review from nkolev92 nkolev92 is a code owner automatically assigned from NuGet/nuget-client-pull-request-auto-assignment

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@nkolev92 @jeffkl