Skip to content

Comments

chore (internal): Use go tools in internal/tools#5035

Open
SoloJacobs wants to merge 5 commits intoprometheus:mainfrom
SoloJacobs:remove-goimports
Open

chore (internal): Use go tools in internal/tools#5035
SoloJacobs wants to merge 5 commits intoprometheus:mainfrom
SoloJacobs:remove-goimports

Conversation

@SoloJacobs
Copy link
Contributor

@SoloJacobs SoloJacobs commented Feb 22, 2026

See commit messages for detailed explanation. Stacks on top of #5033

Pull Request Checklist

Which user-facing changes does this PR introduce?

NONE

This action has multiple flaws:

* It is redundant, since we execute `make lint` in
`.github/workflows/ci.yml`.
* It ignores `make lint`: If we want to remove our build artefacts from
the repository, then we can't run `golangci-lint` without first creating
the artefacts.
* It contains redundant logic, specific to other projects, and refers to
it being synced from https://github.com/prometheus/prometheus (which is
false. `prometheus` does not even use this action anymore).

Signed-off-by: Solomon Jacobs <solomonjacobs@protonmail.com>
* Update Go to 1.26.
* Update minimum Go version to 1.25.0.

Signed-off-by: Solomon Jacobs <solomonjacobs@protonmail.com>
This commit simply runs `golangci-lint run --fix`.

Signed-off-by: Solomon Jacobs <solomonjacobs@protonmail.com>
The usage of this tool was removed in this commit:
a3a156d

Signed-off-by: Solomon Jacobs <solomonjacobs@protonmail.com>
We keep `internal/tools`. This prevents those building from source from
downloading these dependencies and reduces overall dependency conflicts.
The only downside is that build dependencies could in theory affect the
security of alertmanager, albeit this is overly pedantic. The actual
vulnerable code would be checked into our repo anyway.

Related-to: prometheus#4961
Signed-off-by: Solomon Jacobs <solomonjacobs@protonmail.com>
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.

1 participant