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

chore: update to use go1.21 #410

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Conversation

chenrui333
Copy link
Contributor

Description:
With go1.21 release, bump the golang usage/docs to it

Related issue:
n/a

Check list:

  • Mark if documentation changes are required.
  • Mark if tests were added or updated to cover the changes.

@chenrui333 chenrui333 requested a review from a team as a code owner August 10, 2023 13:45
@dsame dsame self-assigned this Aug 11, 2023
@dsame dsame self-requested a review August 11, 2023 08:24
@@ -17,7 +17,7 @@ jobs:
strategy:
matrix:
cache: [false, true]
go: [1.20.1]
go: [1.21.0]
Copy link
Contributor

@dsame dsame Aug 11, 2023

Choose a reason for hiding this comment

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

This job tests is the link created for non-default go installation and it does not make sense to change it. It is just "any version that is not preinstalled in the toolcache"

@dsame
Copy link
Contributor

dsame commented Aug 11, 2023

The check has failed https://github.com/actions/setup-go/actions/runs/5821942042/job/15811878197?pr=410 because the PR should wait till the 1.21 has been deployed to the runners.

@dsame
Copy link
Contributor

dsame commented Aug 14, 2023

I checked the default go is not 21 yet

@chenrui333
Copy link
Contributor Author

rebased to the latest main and rerun the build

@chenrui333
Copy link
Contributor Author

cc @dsame @dmitry-shibanov

@cageyv
Copy link

cageyv commented Sep 14, 2023

cc @dsame @dmitry-shibanov
Anything we could do to help you make it done ?
Look like setup-go is a bit behind now :(

@chenrui333
Copy link
Contributor Author

ping @dsame @dmitry-shibanov

README.md Outdated
Comment on lines 64 to 67
> go-version: '1.21'
> ```
>
> The recommendation is based on the YAML parser's behavior, which interprets non-wrapped values as numbers and, in the case of version 1.20, trims it down to 1.2, which may not be very obvious.
> The recommendation is based on the YAML parser's behavior, which interprets non-wrapped values as numbers and, in the case of version 1.21, trims it down to 1.2, which may not be very obvious.
Copy link
Contributor

Choose a reason for hiding this comment

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

It won't be the case. YAML removes 0 if it is not a string that is why you need to revert these changes.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

or sorry, this with a global replace, let me revert this. good catch.

Copy link
Contributor

Choose a reason for hiding this comment

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

Hello @chenrui333. It looks like you didn't change it.

@dmitry-shibanov
Copy link
Contributor

Thank you for your changes @chenrui333. Could you please revert changes related to actions/checkout and extra spaces.

@chenrui333
Copy link
Contributor Author

sorry about the hassle, I just recommit the change, which is better for review now :) (not sure how I messed up with the master branch merge commit 😮‍💨 )

@chenrui333
Copy link
Contributor Author

Thanks for the patience :)

@Jayzon2019
Copy link

Jayzon2019 commented Sep 21, 2023

Encountered below issue when running Azure DevOps pipeline. Version 1.19 is the current working at my end.

##[error]Failed to download version 1.21. Please verify that the version is valid and resolve any other issues. Error: Unexpected HTTP response: 404

I think, it downloads from this link https://storage.googleapis.com/golang/go1.21.windows-amd64.zip which is empty.

Could somebody help me on this.

Thanks in advance.

@chenrui333
Copy link
Contributor Author

chenrui333 commented Sep 21, 2023

@Jayzon2019 you should use 1.21.0 or 1.21.1 rather than 1.21, which would resolve your issue

@Jayzon2019
Copy link

@chenrui333 . A thousand thanks to you.

I tried 1.21.1 and it was successful. I appreciate the immediate assistance.

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.

5 participants