Latest release needs version bump

[CodeAlDente]

After updating to v1.3.0, dnsx -version still reports v1.2.3.

The updater successfully downloads and verifies the v1.3.0 release:

[INF] Verified Integrity of dnsx_1.3.0_linux_amd64.zip
[INF] dnsx successfully updated 1.2.3 -> 1.3.0 (latest)

https://github.com/projectdiscovery/dnsx/blame/6713390113e9b4ed5f341a4f20cf8166e9fd3835/internal/runner/banner.go#L21

[mr-pmillz]

Also, the latest previous 2 dnsx releases are not available on dockerhub: https://hub.docker.com/r/projectdiscovery/dnsx/tags

The latest available dnsx version on DockerHub is v1.2.2 . @Mzack9999

[ulises2k]

Confirming on v1.3.0, and adding an angle not covered above: the stale const version affects more than the self-updater — it also breaks version reporting for go install builds and for any tool manager that compares version strings (e.g. pdtm).

• go install github.com/projectdiscovery/dnsx/cmd/dnsx@latest (and @v1.3.0) correctly resolve to and build the v1.3.0 source, but the resulting binary still prints Current Version: 1.2.3, because internal/runner/banner.go hardcodes const version = `1.2.3` at the v1.3.0 tag. The official release zip (dnsx_1.3.0_linux_amd64.zip) prints 1.2.3 too, so all three build paths agree — it's purely the source constant.
• As a consequence, pdtm lists it as dnsx (outdated) (1.2.3) ➜ (1.3.0) indefinitely: no matter how many times it reinstalls the real 1.3.0, the binary self-reports 1.2.3 and never matches pdtm's catalog. This produces endless "update" churn (and endless alerts for anyone wiring pdtm updates to notifications).

main is still affected — banner.go at the current default-branch head still has const version = `1.2.3` .

Likely trigger: the GoReleaser modernization in #901 — if the release build no longer injects the version via -ldflags -X ...=version, then the in-source const version becomes the effective version on every build path and simply needs to be bumped per release.

Minimal fix: bump const version to 1.3.0 in internal/runner/banner.go (and going forward, either keep it in sync each release or re-introduce the ldflags version injection at build time).