-
Notifications
You must be signed in to change notification settings - Fork 59
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
Exclude reference packages from CG #1134
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we also revert the manual edits to the projects to reference non-vulnerable versions?
I am planning on doing that in a separate PR (I should have called it out). I want to keep this simple to make it easy to backport. I do not plan on backporting any regen. |
/backport to release/9.0 |
/backport to release/8.0 |
Started backporting to release/9.0: https://github.com/dotnet/source-build-reference-packages/actions/runs/13017542314 |
Started backporting to release/8.0: https://github.com/dotnet/source-build-reference-packages/actions/runs/13017545088 |
@MichaelSimons backporting to "release/9.0" failed, the patch most likely resulted in conflicts: $ git am --3way --empty=keep --ignore-whitespace --keep-non-patch changes.patch
Applying: Exclude reference packages from CG
Using index info to reconstruct a base tree...
M README.md
M azure-pipelines/builds/ci.yml
Falling back to patching base and 3-way merge...
Auto-merging azure-pipelines/builds/ci.yml
CONFLICT (content): Merge conflict in azure-pipelines/builds/ci.yml
Auto-merging README.md
CONFLICT (content): Merge conflict in README.md
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 Exclude reference packages from CG
Error: The process '/usr/bin/git' failed with exit code 128 Please backport manually! |
@MichaelSimons backporting to "release/8.0" failed, the patch most likely resulted in conflicts: $ git am --3way --empty=keep --ignore-whitespace --keep-non-patch changes.patch
Applying: Exclude reference packages from CG
Using index info to reconstruct a base tree...
M README.md
M azure-pipelines/builds/ci.yml
Falling back to patching base and 3-way merge...
Auto-merging azure-pipelines/builds/ci.yml
CONFLICT (content): Merge conflict in azure-pipelines/builds/ci.yml
Auto-merging README.md
CONFLICT (content): Merge conflict in README.md
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 Exclude reference packages from CG
Error: The process '/usr/bin/git' failed with exit code 128 Please backport manually! |
* Exclude reference packages from CG (#1134) * Revert debug setting
Fixes dotnet/source-build#4838