We might want to split out the Go version change into a separate PR.

Ok, yaks shaven, this is ready to go.

Seems like dagger is a bit of technical debt for keeping Go versions up to date as well.

Hmmm, feels strange that we have 2 loggers in the struct now. I'm assuming this is needed somewhere in a different package/repository, could you clarify how you're planning to use this?

Hmmm, feels strange that we have 2 loggers in the struct now. I'm assuming this is needed somewhere in a different package/repository, could you clarify how you're planning to use this?

@SuperQ we're only ever logging at error level here -- maybe we just lean on slog's built in stdlog adapter and avoid the change here altogether? Something like this:

	// make logger with promslog like normal
	slogger := promslog.New(&promslog.Config{})
	// make stdlog adapter from slogger
	logger := slog.NewLogLogger(slogger.Handler(), slog.LevelError)

Bonus points -- log output is still structured

Yea, I suppose using a stdlib adapter would be fine.