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

Update windowsbuilds.go #1155

Merged
merged 1 commit into from
Sep 13, 2021
Merged

Update windowsbuilds.go #1155

merged 1 commit into from
Sep 13, 2021

Conversation

adelina-t
Copy link
Contributor

Updates windowsbuilds to include build number for Windows Server 2022 and corresponding Windows 10 version.

@adelina-t adelina-t requested a review from a team as a code owner September 9, 2021 17:51
@adelina-t
Copy link
Contributor Author

/cc @kevpar

Please help me with a CodeName for WS 2022 & the Windows 10 version that corresponds to this release so I can update the PR. Thank you :)

@@ -35,4 +35,7 @@ const (

// V20H2 corresponds to Windows Server 20H2 (semi-annual channel).
V20H2 = 19042

// corresponds to Windows Server 2022 (ltsc2022), and Windows 10 ().
Copy link
Contributor

@dcantah dcantah Sep 9, 2021

Choose a reason for hiding this comment

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

Start the comment with V2022 to satisfy godoc/go tooling. Wondering if we should name this V21H2 though

Copy link
Member

Choose a reason for hiding this comment

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

I think V21H2 is reasonable given it's the version identifier used here: https://docs.microsoft.com/en-us/windows-server/get-started/windows-server-release-info

Copy link
Contributor

Choose a reason for hiding this comment

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

Ok cool

@dcantah
Copy link
Contributor

dcantah commented Sep 9, 2021

@adelina-t Thanks for this by the way! I was just mentioning I was going to add it yesterday 😂

@adelina-t adelina-t force-pushed the patch-1 branch 2 times, most recently from e3caf99 to 83641ba Compare September 10, 2021 11:55
@dcantah
Copy link
Contributor

dcantah commented Sep 10, 2021

@adelina-t You're going to have to run go mod vendor + go mod tidy in the /test directory in this repo, and then this should be good to go! The reason is in the README now https://github.com/microsoft/hcsshim/blob/master/README.md#contributing

@dcantah
Copy link
Contributor

dcantah commented Sep 10, 2021

@katiewasnothere Is the failure just because we need a rebase here?

@adelina-t
Copy link
Contributor Author

@katiewasnothere Is the failure just because we need a rebase here?

Might be. Let me try a rebase

@dcantah
Copy link
Contributor

dcantah commented Sep 10, 2021

Yea, I'd try a rebase and go mod vendor + tidy again.

@adelina-t
Copy link
Contributor Author

adelina-t commented Sep 10, 2021

Yea, I'd try a rebase and go mod vendor + tidy again.

Rebased & pushed, but no diff on mod vendor + tidy. Let's see though.

@dcantah
Copy link
Contributor

dcantah commented Sep 10, 2021

@adelina-t What version of go are you on? Is it < 1.15?

Updates windowsbuilds to include build number for Windows Server 2022.

Signed-off-by: Adelina Tuvenie <[email protected]>
@adelina-t
Copy link
Contributor Author

adelina-t commented Sep 13, 2021

@adelina-t What version of go are you on? Is it < 1.15?

go version go1.16.7

I've cherrypicked the commit on another machine, go mod + tidy & checked with Verify-GoModules.ps1, should be ok now. No ideea what the problem was on the other machine. Go version was the same on both.

Copy link
Contributor

@dcantah dcantah left a comment

Choose a reason for hiding this comment

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

Huzzah everything's green now, lgtm.

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.

3 participants