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/8.0-staging] Pin the 6.0.x down-level versions to 6.0.36 #110329

Merged
merged 2 commits into from
Dec 2, 2024

Conversation

lewing
Copy link
Member

@lewing lewing commented Dec 2, 2024

No description provided.

@dotnet-issue-labeler dotnet-issue-labeler bot added the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label Dec 2, 2024
@lewing lewing requested a review from carlossanlop December 2, 2024 20:04
@lewing lewing requested a review from marcpopMSFT December 2, 2024 20:04
@lewing lewing added area-Workloads Workloads like wasm-tools and removed needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners labels Dec 2, 2024
@lewing lewing requested a review from akoeplinger December 2, 2024 20:06
@lewing lewing added the Servicing-approved Approved for servicing release label Dec 2, 2024
@carlossanlop
Copy link
Member

The CI is not done and I see one browser failure but it seems pre-existing: #104827

@lewing
Copy link
Member Author

lewing commented Dec 2, 2024

the failures here can't be related to the PR

@carlossanlop carlossanlop merged commit 0a843bb into dotnet:release/8.0-staging Dec 2, 2024
8 checks passed
@lewing lewing deleted the pin-6-in-8 branch December 2, 2024 22:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-Workloads Workloads like wasm-tools Servicing-approved Approved for servicing release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants