After releasing go1.24, we can manage tools as dependencies!

Here is very good step by step article about how to do it https://www.alexedwards.net/blog/how-to-manage-tool-dependencies-in-go-1.24-plus

Also it includes example how to add tools to seperate go.mod file (TIL!)

FYI: https://semgrep.dev/blog/2025/popular-github-action-tj-actionschanged-files-is-compromised/

https://www.stepsecurity.io/blog/harden-runner-detection-tj-actions-changed-files-action-is-compromised

"Programming Is Like S*x: One mistake and you have to support it for the rest of your life." — Michael Sinz

😭😭😭

Interesting approach by Russ for finding bugs by diff code coverage profiles between faing and success exectuon:

https://research.swtch.com/diffcover

Classics https://status.redhat.com/

> Quay.io has been moved to read-only mode while we work to implement a fix. During this time Pulls will continue to work, however, Pushes will be disabled until a fix is implemented. There is currently no timeline for Push restoration.

> The issue has been identified. A primary key in the database has reached maximum value. We are currently working on validating a fix.

Nice satire article https://www.justfuckingcode.com/ 🙂 Kinda true in many directions 🙂

Hey k8s/containers users!

Go 1.25 not yet released but will be container aware of GOMAXPROCS https://tip.golang.org/doc/go1.25#container-aware-gomaxprocs