Skip to content
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

Cleanup release preparation stage #4744

Merged
merged 1 commit into from
Jun 27, 2023

Conversation

jander-msft
Copy link
Member

Summary

Manual backport of #4175 to release/7.x

Example non-release build: https://dev.azure.com/dnceng/internal/_build/results?buildId=2209662&view=results
Example test release build: https://dev.azure.com/dnceng/internal/_build/results?buildId=2209688&view=results

Release Notes Entry

@jander-msft jander-msft added the backport Pull requests that are backports of another pull request label Jun 26, 2023
@ghost ghost added the needs-review label Jun 26, 2023
@jander-msft jander-msft added servicing-patch Servicing fixes that is targeted for a patch release (0.0.x version) servicing-minor Servicing fixes that is targeted for a minor release (0.x.0 version) labels Jun 26, 2023
@ghost ghost removed the needs-review label Jun 26, 2023
@jander-msft jander-msft changed the title [release/7.x] Cleanup release preparation stage Cleanup release preparation stage Jun 27, 2023
@jander-msft jander-msft merged commit a4a599c into dotnet:main Jun 27, 2023
21 checks passed
@jander-msft jander-msft deleted the cleanup-release-prep-7.x branch June 27, 2023 01:21
@jander-msft
Copy link
Member Author

/backport to release/7.2

@github-actions
Copy link
Contributor

Started backporting to release/7.2: https://github.com/dotnet/dotnet-monitor/actions/runs/5384715520

@github-actions
Copy link
Contributor

@jander-msft backporting to release/7.2 failed, the patch most likely resulted in conflicts.

Please backport manually using one of the below commands, followed by git am --continue once the merge conflict has been resolved.

PowerShell

(Invoke-WebRequest "https://github.com/dotnet/dotnet-monitor/commit/a4a599c4a09a61bf527f924d9e502cbeea32c302.patch").Content | git am --3way --ignore-whitespace --exclude="documentation/**.md" --keep-non-patch

Bash

curl -sSL "https://github.com/dotnet/dotnet-monitor/commit/a4a599c4a09a61bf527f924d9e502cbeea32c302.patch" | git am --3way --ignore-whitespace --exclude="documentation/**.md" --keep-non-patch

git am error output:

$ git am --3way --ignore-whitespace --exclude="documentation/**.md" --keep-non-patch changes.patch

Patch format detection failed.
Error: The process '/usr/bin/git' failed with exit code 128

@jander-msft
Copy link
Member Author

/backport to release/6.x

@github-actions
Copy link
Contributor

Started backporting to release/6.x: https://github.com/dotnet/dotnet-monitor/actions/runs/5384720299

@github-actions
Copy link
Contributor

@jander-msft backporting to release/6.x failed, the patch most likely resulted in conflicts.

Please backport manually using one of the below commands, followed by git am --continue once the merge conflict has been resolved.

PowerShell

(Invoke-WebRequest "https://github.com/dotnet/dotnet-monitor/commit/a4a599c4a09a61bf527f924d9e502cbeea32c302.patch").Content | git am --3way --ignore-whitespace --exclude="documentation/**.md" --keep-non-patch

Bash

curl -sSL "https://github.com/dotnet/dotnet-monitor/commit/a4a599c4a09a61bf527f924d9e502cbeea32c302.patch" | git am --3way --ignore-whitespace --exclude="documentation/**.md" --keep-non-patch

git am error output:

$ git am --3way --ignore-whitespace --exclude="documentation/**.md" --keep-non-patch changes.patch

Patch format detection failed.
Error: The process '/usr/bin/git' failed with exit code 128

@jander-msft jander-msft removed servicing-patch Servicing fixes that is targeted for a patch release (0.0.x version) servicing-minor Servicing fixes that is targeted for a minor release (0.x.0 version) backport Pull requests that are backports of another pull request labels Jun 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants