all: update mvdan/gofumpt to v0.12.0

[renovate]

This PR contains the following updates:

Package	Update	Change
mvdan/gofumpt	minor	v0.9.2 → v0.12.0

---

Release Notes

mvdan/gofumpt (mvdan/gofumpt)

v0.12.0

Compare Source

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

Compare Source

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

Compare Source

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

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • Between 12:00 AM and 03:59 AM, only on Monday (* 0-3 * * 1)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.