Skip to content

Tags: mvdan/gofumpt

Tags

v0.7.0

Toggle v0.7.0's commit message

Verified

This tag was signed with the committer’s verified signature.
mvdan Daniel Martí
release v0.7.0

v0.6.0

Toggle v0.6.0's commit message

Verified

This tag was signed with the committer’s verified signature.
mvdan Daniel Martí
release v0.6.0

v0.5.0

Toggle v0.5.0's commit message

Verified

This tag was signed with the committer’s verified signature.
mvdan Daniel Martí
release v0.5.0

v0.4.0

Toggle v0.4.0's commit message
write changelog for v0.4.0

Note that we're starting to recommend a particular Go version for
building gofumpt, as that is the go/printer version we've tested the
most with, and a consistent version will also bring consistent behavior.

See #244.

v0.3.1

Toggle v0.3.1's commit message
prepare changelog for v0.3.1

And start adding links for the major changes, so any interested users
can read more into each topic.

We also make the release links use the "v" prefix for consistency.

v0.3.0

Toggle v0.3.0's commit message
write changelog for v0.3.0

While writing it, I also noticed that the second change for #73,
where we now separate ") {" even if there's no empty line,
wasn't documented in the README. It now is.

v0.2.1

Toggle v0.2.1's commit message
write changelog for v0.2.1

v0.2.0

Toggle v0.2.0's commit message
ready changelog for v0.2.0

v0.1.1

Toggle v0.1.1's commit message
add a changelog file, prepping for v0.1.1

The v0.1.0 notes are copied from the GitHub release.

v0.1.0

Toggle v0.1.0's commit message
add a -version flag to gofumpt

This allows for versioned go get/install commands to bundle the module
version in the binary, then the version flag can print it as-is.

Prebuilt binaries will also include it via ldflags.

Not for gofumports, since its days are counted.

For #99.