Closed thaJeztah closed 1 year ago
actually; let me change go.mod to go1.19 (as 1.18 doesn't have that fix)
Patch and project coverage have no change.
Comparison is base (
da93839
) 55.55% compared to head (3d84f97
) 55.55%.:exclamation: Current head 3d84f97 differs from pull request most recent head 37c4a6b. Consider uploading reports for the commit 37c4a6b to get more accurate results
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.
the "golang.org/x/sys/execabs" package was introduced to address a security issue on Windows, and changing the default behavior of os/exec was considered a breaking change. go1.19 applied the behavior that was previously implemented in the execabs package;
from the release notes: https://go.dev/doc/go1.19#os-exec-path
With those changes, we no longer need to use the execabs package, and we can switch back to os/exec.