How to Handle Breaking Changes in Go Modules (v2+)

Core
2026-04-17T12:05:42+00:00
Use the `godebug` directive in your `go.mod` or `go.work` file to explicitly opt into legacy behavior when upgrading the Go toolchain. Add a `godebug` block to your module file to override defaults for specific settings like `panicnil` or `tarinsecurepath`.

How to Handle Breaking Changes in Go Modules (v2+)

Use the godebug directive in your go.mod or go.work file to explicitly opt into legacy behavior when upgrading the Go toolchain. Add a godebug block to your module file to override defaults for specific settings like panicnil or tarinsecurepath.

module example.com/myapp

go 1.23

godebug (
	default=go1.21
	panicnil=1
	tarinsecurepath=0
)

Alternatively, set the GODEBUG environment variable before running your program to apply settings at runtime without changing source files.

export GODEBUG=panicnil=1,tarinsecurepath=0
go run ./cmd/myapp