Skip to content

Conversation

@ddelnano
Copy link
Member

@ddelnano ddelnano commented Feb 10, 2025

Summary: Upgrade rules_go to v0.47.1 for go 1.22 support

The work to remove our dependence on go 1.16 will be complete soon (once #2108 is merged). With that done, we can upgrade our go dependencies and go version. This rules_go change is needed to support go 1.22 as there was an assembler fix in v0.46.0 (bazel-contrib/rules_go#3756 specifically).

This was the most recent rules_go version I could upgrade to without dealing with breaking changes. I'll revisit upgrading this to a newer version soon, but my primary goal was to be able to upgrade go and our go deps.

Relevant Issues: N/A

Type of change: /kind cleanup

Test Plan: Existing tests and verified my branch to add go 1.22 as a supported version builds properly

Signed-off-by: Dom Del Nano <ddelnano@gmail.com>
@ddelnano ddelnano merged commit b122242 into pixie-io:main Feb 11, 2025
32 checks passed
@ddelnano ddelnano deleted the ddelnano/upgrade-rules_go_to-go-1-22-compatible-version branch February 11, 2025 06:54
ddelnano added a commit to ddelnano/pixie that referenced this pull request Aug 6, 2025
Summary: Upgrade rules_go to v0.47.1 for go 1.22 support

The work to remove our dependence on go 1.16 will be complete soon (once
pixie-io#2108 is merged). With that done, we can upgrade our go dependencies and
go version. This rules_go change is needed to support go 1.22 as there
was an assembler fix in
[v0.46.0](https://github.com/bazel-contrib/rules_go/releases/tag/v0.46.0)
(bazel-contrib/rules_go#3756 specifically).

This was the most recent rules_go version I could upgrade to without
dealing with breaking changes. I'll revisit upgrading this to a newer
version soon, but my primary goal was to be able to upgrade go and our
go deps.

Relevant Issues: N/A

Type of change: /kind cleanup

Test Plan: Existing tests and verified my branch to add go 1.22 as a
supported version builds properly

Signed-off-by: Dom Del Nano <ddelnano@gmail.com>
GitOrigin-RevId: b122242
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.

2 participants