-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Update package version #17018
Update package version #17018
Conversation
57406e0
to
5dc4478
Compare
This pull request has merge conflicts. Please resolve those before requesting a review. |
/backport to release/2.1 |
Started backporting to release/2.1: https://github.com/OrchardCMS/OrchardCore/actions/runs/12016454683 |
@MikeAlhayek backporting to release/2.1 failed, the patch most likely resulted in conflicts: $ git am --3way --empty=keep --ignore-whitespace --keep-non-patch changes.patch
Applying: Update package version
Using index info to reconstruct a base tree...
M Directory.Packages.props
Falling back to patching base and 3-way merge...
Auto-merging Directory.Packages.props
CONFLICT (content): Merge conflict in Directory.Packages.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 advice.mergeConflict false"
Patch failed at 0001 Update package version
Error: The process '/usr/bin/git' failed with exit code 128 Please backport manually! |
@MikeAlhayek an error occurred while backporting to release/2.1, please check the run log for details! Error: git am failed, most likely due to a merge conflict. |
No description provided.