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(deps): bump go version to 1.23.1 #1474

Merged
merged 11 commits into from
Sep 17, 2024
Merged

Conversation

rach-id
Copy link
Member

@rach-id rach-id commented Sep 11, 2024

Description

Bumps go version to 1.23.1

@rach-id rach-id self-assigned this Sep 11, 2024
@rach-id rach-id requested a review from a team as a code owner September 11, 2024 08:15
@rach-id rach-id requested review from cmwaters and staheri14 and removed request for a team September 11, 2024 08:15
@rach-id rach-id marked this pull request as draft September 11, 2024 08:24
@rach-id rach-id marked this pull request as draft September 11, 2024 08:24
@rach-id rach-id marked this pull request as draft September 11, 2024 08:24
@rach-id rach-id marked this pull request as ready for review September 11, 2024 12:38
rootulp
rootulp previously approved these changes Sep 11, 2024
Copy link
Collaborator

@rootulp rootulp left a comment

Choose a reason for hiding this comment

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

LGTM! golangci-lint bump looks like it surfaced some lint errors

.github/workflows/lint.yml Outdated Show resolved Hide resolved
rootulp
rootulp previously approved these changes Sep 11, 2024
Copy link
Collaborator

@rootulp rootulp left a comment

Choose a reason for hiding this comment

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

[optional] instead of adding /nolint:gosec everywhere, we can disable that linter in .golangci.yml until we pull from upstream a copy of this codebase that does address those lint warnings

@rach-id
Copy link
Member Author

rach-id commented Sep 11, 2024

we can disable that linter in .golangci.yml until we pull from

I didn't want to do it so in case future contributions are hitting any cases where we should be aware. The current code worked for years without the checks, we can assume it's fine. But new code might need the safe conversions. That's why I left it

- name: Create a file with all the pkgs
run: go list ./... > pkgs.txt
- name: Split pkgs into 4 files
run: split -d -n l/4 pkgs.txt pkgs.txt.part.
# cache multiple
- uses: actions/upload-artifact@v3
- uses: actions/upload-artifact@v4
Copy link
Contributor

Choose a reason for hiding this comment

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

Just curious to know whether this is also necessary for the Go version upgrade to work? or it is an independent change?

Copy link
Member Author

Choose a reason for hiding this comment

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

All are necessary because they don't support the new version of go, unless I am missing something

@rach-id rach-id merged commit 619d319 into v0.34.x-celestia Sep 17, 2024
21 checks passed
@rach-id rach-id deleted the bump-go-version branch September 17, 2024 18:30
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