bump version to 1.3.0

[Mzack9999]

v1.3.0 was tagged without updating the hardcoded version in banner.go, so -version and the updater still reported 1.2.3 after a successful update. dnsx has no version-bump workflow (same as httpx/nuclei), so this sets the const to 1.3.0.

Already published v1.3.0 binaries stay wrong until a new release is cut. Closes #1002.

Summary by CodeRabbit

• Chores
  • Updated the application version to 1.3.0.
  • Update checks and downloads now use the latest version identifier.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: e1cbad6f-6002-476a-b076-350ae79a417e

📥 Commits

Reviewing files that changed from the base of the PR and between 1918ce7 and b6e5d6f.

📒 Files selected for processing (1)

• internal/runner/banner.go

---

Walkthrough

The runner’s package-level version constant is updated from 1.2.3 to 1.3.0, changing the version used by version reporting and update callbacks.

Changes

Release version update

Layer / File(s)	Summary
Update runner version constant internal/runner/banner.go	The package-level version constant now contains 1.3.0 instead of 1.2.3.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Poem

A rabbit nibbles version three,
“One point three!” it sings with glee.
The banner blooms, the updater knows,
A fresher release now gently flows.
Hop, hop—new numbers grow!

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the main change: bumping the dnsx version to 1.3.0.
Linked Issues check	✅ Passed	The version bump in banner.go matches issue #1002 by making dnsx report v1.3.0 and updating the banner/updater version.
Out of Scope Changes check	✅ Passed	The PR only changes the hardcoded version constant, with no unrelated code changes visible.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch bump-version-string

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}