v2.9.2 bump

[rvagg]

🤷 is this patch worthy or does mateirally changing the output of someone's logs count for more than that? @lidel what do you think?

[github-actions]

Suggested tag: v2.9.2

Comparing to: v2.9.1 (diff)

Changes in configuration file(s):

diff --git a/go.mod b/go.mod
index 7220406..6a958b8 100644
--- a/go.mod
+++ b/go.mod
@@ -1,11 +1,11 @@
 module github.com/ipfs/go-log/v2
 
-go 1.24
+go 1.25
 
 require (
-	github.com/mattn/go-isatty v0.0.20
+	github.com/mattn/go-isatty v0.0.22
 	github.com/stretchr/testify v1.11.1
-	go.uber.org/zap v1.27.1
+	go.uber.org/zap v1.28.0
 )
 
 require (

gorelease says:

# summary
v2.9.2 is a valid semantic version for this release.

gocompat says:

HEAD is now at 3fc6f96 new version (#179)
Previous HEAD position was 3fc6f96 new version (#179)
Switched to branch 'master'
Your branch is up to date with 'origin/master'.

Automatically created GitHub Release

A draft GitHub Release has been created.
It is going to be published when this PR is merged.
You can modify its' body to include any release notes you wish to include with the release.

[gammazero]

I think a patch release is reasonable here as this fixes an interaction between slog and zap, and is not adding any new feature. I would not consider the changes to the log output to constitute a behavior change worthy of a bigger version bump, because it is essentially fixing broken output, and nothing should rely on that particular output, especially since it is generally empty.

No problems with kubo: ipfs/kubo#11325