This was the root cause of the Go module lookup failure: the rename commit was pushed to the PR branch after PR #21 was merged, so main still declared module github.com/hits/ExploreDNS. This mismatch caused Go module lookups to fail regardless of env var configuration.
Cherry-picks commit 570c543 (go.mod module path rename) onto main.
This was the root cause of the Go module lookup failure: the rename commit was pushed to the PR branch after PR #21 was merged, so main still declared `module github.com/hits/ExploreDNS`. This mismatch caused Go module lookups to fail regardless of env var configuration.
- Replace hardcoded go-version '1.24' with go-version-file: 'go.mod' so CI
always uses the toolchain version that matches the module's requirements
(go.mod currently declares go 1.25.6)
- Fix 'Check internal package coverage' step: update grep pattern from
old module path 'github.com/hits/ExploreDNS/internal' to the renamed
path 'gitea.hansenits.com.au/hits/ExploreDNS/internal'
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: multica-agent <github@multica.ai>
- Keep go-version-file: 'go.mod' from PR (reads Go version from go.mod)
- Keep gitea.hansenits.com.au module path in coverage check
- Pick up .gitignore bin/* entry from main
- go.mod: keep go 1.24.0 directive from main (GOTOOLCHAIN=local)
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: multica-agent <github@multica.ai>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Cherry-picks commit
570c543(go.mod module path rename) onto main.This was the root cause of the Go module lookup failure: the rename commit was pushed to the PR branch after PR #21 was merged, so main still declared
module github.com/hits/ExploreDNS. This mismatch caused Go module lookups to fail regardless of env var configuration.