Skip to content

[release/7.0][workloads] Bump the runtime net6 versions for GA #76270

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

Merged
merged 1 commit into from
Oct 5, 2022

Conversation

lewing
Copy link
Member

@lewing lewing commented Sep 27, 2022

No description provided.

@ghost
Copy link

ghost commented Sep 27, 2022

I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label.

@ghost ghost assigned lewing Sep 27, 2022
@lewing lewing marked this pull request as draft September 27, 2022 20:44
@steveisok
Copy link
Member

Pre-approving for when emsdk comes along.

@lewing lewing added this to the 7.0.0 milestone Sep 27, 2022
@ghost
Copy link

ghost commented Sep 27, 2022

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

Issue Details

null

Author: lewing
Assignees: lewing
Labels:

area-Infrastructure

Milestone: 7.0.0

@lewing lewing marked this pull request as ready for review September 28, 2022 15:05
@lewing
Copy link
Member Author

lewing commented Sep 28, 2022

https://dotnet.github.io/core-eng/helix-workitem-deadletter.txt :(

@carlossanlop
Copy link
Contributor

https://dotnet.github.io/core-eng/helix-workitem-deadletter.txt :(

@lewing should we close and reopen?

Pre-approving for when emsdk comes along.

@steveisok what's the action I should take here? (assuming the deadletter error goes away)

@steveisok
Copy link
Member

steveisok commented Sep 28, 2022

@steveisok what's the action I should take here? (assuming the deadletter error goes away)

@lewing, do we need to wait on emsdk for anything? I initially thought we did, but I may be mistaken.

@lewing
Copy link
Member Author

lewing commented Sep 28, 2022

depends if we want to wait for 6.0.x branding to make a 6.0.11 runtime?

@steveisok
Copy link
Member

depends if we want to wait for 6.0.x branding to make a 6.0.11 runtime?

I guess it wouldn't be a bad idea to try to line things up.

@carlossanlop
Copy link
Contributor

I guess it wouldn't be a bad idea to try to line things up.

Talked with @steveisok about this. We can merge this after October 4, and we will have a window of 6 days to do so:

@lewing
Copy link
Member Author

lewing commented Oct 5, 2022

blocked on #76620 now

@lewing lewing added the blocked Issue/PR is blocked on something - see comments label Oct 5, 2022
@lewing
Copy link
Member Author

lewing commented Oct 5, 2022

@marcpopMSFT @mmitche we really need a better way to deal with these version string only dependencies that break so many things

@carlossanlop
Copy link
Contributor

blocked on #76620 now

@lewing I merged the 6.0 branding PR. Do I need to wait for a dependency to be generated or do I just merge this right away?

@carlossanlop carlossanlop removed the blocked Issue/PR is blocked on something - see comments label Oct 5, 2022
@carlossanlop carlossanlop merged commit 5147f6f into dotnet:release/7.0 Oct 5, 2022
@lewing lewing deleted the workload-6-rtm branch October 6, 2022 17:04
@ghost ghost locked as resolved and limited conversation to collaborators Nov 5, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants