chore(deps): bump mvdan.cc/gofumpt from 0.7.0 to 0.12.0 in /tools

[dependabot]

Bumps mvdan.cc/gofumpt from 0.7.0 to 0.12.0.

Release notes

Sourced from mvdan.cc/gofumpt's releases.

v0.12.0

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

A standard library import carrying a doc or inline comment is no longer moved into the top import group, as the comment stayed behind and ended up detached at the bottom of the group. See #289.

Moving a standard library import up no longer leaves an empty line where it used to be, which split the remaining imports into extra groups. See #225.

A copyright header or package doc no longer makes gofumpt treat a single-line first declaration as multi-line, adding an empty line after it.

An assignment whose right-hand side is separated by a comment is now left alone, as merging the lines produced output which gofmt would change back.

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

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

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

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

... (truncated)

Changelog

Sourced from mvdan.cc/gofumpt's changelog.

[v0.12.0] - 2026-09-07

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

A standard library import carrying a doc or inline comment is no longer moved into the top import group, as the comment stayed behind and ended up detached at the bottom of the group. See #289.

Moving a standard library import up no longer leaves an empty line where it used to be, which split the remaining imports into extra groups. See #225.

A copyright header or package doc no longer makes gofumpt treat a single-line first declaration as multi-line, adding an empty line after it.

An assignment whose right-hand side is separated by a comment is now left alone, as merging the lines produced output which gofmt would change back.

[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.

... (truncated)

Commits

• 3e07e7e CHANGELOG: add entry for v0.12.0
• e0311de update deps
• 6249406 fix three out-of-date comments
• b7fd50a add AGENTS.md documenting the project for coding agents
• 05e0adf format: don't merge assignment lines across a comment
• 360940c testdata: add regression test for assignment newlines with comments
• 409d850 format: don't let header comments make the first decl multi-line
• 6ea8a37 testdata: add regression test for header comments before the first decl
• b31bdf4 format: don't leave an empty line where a moved std import was
• ce9a249 format: don't move std imports carrying comments
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)