chore(deps): bump mvdan.cc/gofumpt from 0.9.1 to 0.11.0

[dependabot]

Bumps mvdan.cc/gofumpt from 0.9.1 to 0.11.0.

Release notes

Sourced from mvdan.cc/gofumpt's releases.

v0.11.0

Like v0.10.0, this release is based on Go 1.26's gofmt, and requires Go 1.25 or later.

The multi-line function call rule introduced in v0.10.0 proved controversial, so it is now the extra rule balance_calls, disabled by default. It is also narrowed to only place the closing parenthesis on its own line when the opening parenthesis ends a line. See #74.

Avoid crashing when compiled with tinygo for Wasm, which lacks recover support, by detecting commented-out code without the parser's bailout panic. See #230.

Produce stable output in a single pass when a lone var declaration is adjacent to a single-element var group, which previously required a second run. See #355.

Keep the parentheses around an expression which begins with a composite literal of the form T{...}, such as (s{}.Foo()), as they are required when the expression starts an if, for, or switch clause. See #356.

Consider becoming a sponsor if you benefit from the work that went into this release!

Binaries built on go version go1.26.5 linux/amd64 with:

CGO_ENABLED=0 go build -trimpath -ldflags="-w -s"

v0.10.0

This release is based on Go 1.26's gofmt, and requires Go 1.25 or later.

A new rule is introduced to drop unnecessary parentheses around expressions where the inner expression is unambiguous on its own, such as f((3)). Parentheses are kept where they are useful, such as on binary expressions. See #44.

A new rule is introduced to require multi-line function calls to match the opening and closing parenthesis in terms of the use of newlines. See #74.

The -extra flag now accepts a comma-separated list of rule names to enable individual extra rules, rather than enabling all of them at once. See #339.

The following changes are included as well:

• Avoid crashing on go.mod files without a module directive - #350
• Avoid failing when an ignored directory cannot be read - #351
• Avoid prefixing more kinds of commented-out Go code with spaces - #230
• Avoid prefixing a shebang comment with a space - #237
• Narrow the newlines on assignments rule to ignore complex cases - #354
• Fix three bugs which caused a second gofumpt run to make changes - #132, #345

Binaries built on go version go1.26.2 linux/amd64 with:

CGO_ENABLED=0 go build -trimpath -ldflags="-w -s"

Consider becoming a sponsor if you benefit from the work that went into this release! New tiers with rewards are available as well.

v0.9.2

This release moves the "clothe naked returns" rule under gofumpt -extra, following the discussion in mvdan/gofumpt#285.

Binaries built on go version go1.25.3 linux/amd64 with:

CGO_ENABLED=0 go build -trimpath -ldflags="-w -s"

Consider becoming a sponsor if you benefit from the work that went into this release!

... (truncated)

Changelog

Sourced from mvdan.cc/gofumpt's changelog.

[v0.11.0] - 2026-07-27

Like v0.10.0, this release is based on Go 1.26's gofmt, and requires Go 1.25 or later.

The multi-line function call rule introduced in v0.10.0 proved controversial, so it is now the extra rule balance_calls, disabled by default. It is also narrowed to only place the closing parenthesis on its own line when the opening parenthesis ends a line. See #74.

Avoid crashing when compiled with tinygo for Wasm, which lacks recover support, by detecting commented-out code without the parser's bailout panic. See #230.

Produce stable output in a single pass when a lone var declaration is adjacent to a single-element var group, which previously required a second run. See #355.

Keep the parentheses around an expression which begins with a composite literal of the form T{...}, such as (s{}.Foo()), as they are required when the expression starts an if, for, or switch clause. See #356.

[v0.10.0] - 2026-05-04

This release is based on Go 1.26's gofmt, and requires Go 1.25 or later.

A new rule is introduced to drop unnecessary parentheses around expressions where the inner expression is unambiguous on its own, such as f((3)). Parentheses are kept where they are useful, such as on binary expressions. See #44.

A new rule is introduced to require multi-line function calls to match the opening and closing parenthesis in terms of the use of newlines. See #74.

The -extra flag now accepts a comma-separated list of rule names to enable individual extra rules, rather than enabling all of them at once. See #339.

The following changes are included as well:

• Avoid crashing on go.mod files without a module directive - #350
• Avoid failing when an ignored directory cannot be read - #351
• Avoid prefixing more kinds of commented-out Go code with spaces - #230
• Avoid prefixing a shebang comment with a space - #237
• Narrow the newlines on assignments rule to ignore complex cases - #354
• Fix three bugs which caused a second gofumpt run to make changes - #132, #345

Commits

• 5dca7d8 CHANGELOG: add entry for v0.11.0
• 3fc6a0d update deps
• afd4fd5 format: move the multi-line call parens rule behind -extra
• 2d7b4e6 format: make var decl merge idempotent for the empty-line separator
• b1173bf format: add regression test for non-idempotent var decl merge
• 9c29374 format: keep parens required around composite literal in clause
• 2443c24 format: add regression test for parens around composite literal in clause
• cc84354 format: merge adjacent var line and single-element group in one pass
• c238c0d format: go fix -all
• b13b3a7 format: avoid parser bailout panic when detecting commented-out code
• Additional commits viewable in compare view