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

[release/7.0] Reintroduce typo in ICorDebug public API names #76967

Merged
merged 2 commits into from
Oct 13, 2022

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Oct 12, 2022

Backport of #76966 to release/7.0

/cc @jkotas

Customer Impact

Build break after updating to .NET 7 ICorDebug header files. The build break was introduced by attempt to fix a typo in publicly documented API name. The typo fix is being reverted by this change.

Testing

Standard CI testing, verified that the API name matches the documented name.

Risk

Low

IMPORTANT: Is this backport for a servicing release? If so and this change touches code that ships in a NuGet package, please make certain that you have added any necessary package authoring and gotten it explicitly reviewed.

@ghost
Copy link

ghost commented Oct 12, 2022

Tagging subscribers to this area: @tommcdon
See info in area-owners.md if you want to be subscribed.

Issue Details

Backport of #76966 to release/7.0

/cc @jkotas

Customer Impact

Testing

Risk

IMPORTANT: Is this backport for a servicing release? If so and this change touches code that ships in a NuGet package, please make certain that you have added any necessary package authoring and gotten it explicitly reviewed.

Author: github-actions[bot]
Assignees: -
Labels:

area-Diagnostics-coreclr

Milestone: -

@jkotas jkotas requested review from noahfalk and tommcdon October 12, 2022 20:38
@carlossanlop
Copy link
Member

@mmitche do we still have runway to include this in GA?

@carlossanlop carlossanlop added the Servicing-approved Approved for servicing release label Oct 12, 2022
@carlossanlop
Copy link
Member

Approved by Tactics via email.

@carlossanlop carlossanlop added this to the 7.0.x milestone Oct 12, 2022
Copy link
Member

@jeffschwMSFT jeffschwMSFT left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

approved

@mmitche
Copy link
Member

mmitche commented Oct 12, 2022

Yes

@carlossanlop carlossanlop modified the milestones: 7.0.x, 7.0.0 Oct 12, 2022
@carlossanlop
Copy link
Member

Cool, thanks. Will merge after checking the CI.

@carlossanlop
Copy link
Member

Re-running the failed CI leg. There were network issues.

@carlossanlop
Copy link
Member

The CI re-run had one failure, but unrelated and I've seen it before: #76906

Approved by Tactics and signed off by lots of folks. Merging now. :shipit:

@carlossanlop carlossanlop merged commit c7b59fc into release/7.0 Oct 13, 2022
@carlossanlop carlossanlop deleted the backport/pr-76966-to-release/7.0 branch October 13, 2022 18:02
@ghost ghost locked as resolved and limited conversation to collaborators Nov 12, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants