-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Upgrade Microsoft.VisualStudio.SolutionPersistence
to 1.0.52
#11549
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
/backport to vs17.14 |
Started backporting to vs17.14: https://github.com/dotnet/msbuild/actions/runs/13788530939 |
@maridematte an error occurred while backporting to "vs17.14", please check the run log for details! Error: @maridematte is not a repo collaborator, backporting is not allowed. If you're a collaborator please make sure your dotnet team membership visibility is set to Public on https://github.com/orgs/dotnet/people?query=maridematte |
/backport to vs17.14 |
Started backporting to vs17.14: https://github.com/dotnet/msbuild/actions/runs/13788843084 |
@maridematte backporting to "vs17.14" failed, the patch most likely resulted in conflicts: $ git am --3way --empty=keep --ignore-whitespace --keep-non-patch changes.patch
Applying: upgrade Microsoft.VisualStudio.SolutionPersistence to 1.0.52
Using index info to reconstruct a base tree...
M eng/Versions.props
Falling back to patching base and 3-way merge...
Auto-merging eng/Versions.props
CONFLICT (content): Merge conflict in eng/Versions.props
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config set advice.mergeConflict false"
Patch failed at 0001 upgrade Microsoft.VisualStudio.SolutionPersistence to 1.0.52
Error: The process '/usr/bin/git' failed with exit code 128 Please backport manually! |
Follow-up to #11538