Skip to content

Conversation

pjreiniger
Copy link
Contributor

I noticed that me an Austin both seem to have more recent version of buildifier locally which is causing extraneous changes in our PR's. This updates it to the latest version as of today.

@pjreiniger pjreiniger requested a review from a team as a code owner July 3, 2025 21:40
id: go

- name: Install Buildifier
run: |
cd $(mktemp -d)
GO111MODULE=on go get github.com/bazelbuild/buildtools/buildifier@6.0.0
GO111MODULE=on go install github.com/bazelbuild/buildtools/buildifier@v0.0.0-20250703141324-fdc626802fbc
Copy link
Member

Choose a reason for hiding this comment

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

Is it typical to run pre-release versions like this locally?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I have no idea how go install works, but it wouldn't find 8.2.1. When I locally ran the instructions from the buildifier docs, that was the version that got spit out

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Also if you run go install github.com/bazelbuild/buildtools/[email protected] it prints out that it installed v0.0.0-20230109211708-de1a539b56e7

Copy link
Member

Choose a reason for hiding this comment

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

Should we use the pre-built binaries instead?

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