[Jason10191019999]

Summary

• When no matching tag exists, treat the default fromCommit=HEAD as an unspecified starting point instead of producing an empty HEAD...HEAD range.
• Only pass from and to to simple-git when a starting commit is present, allowing its default full-history log for a first release.
• Preserve explicit commit ranges and tagged-release behavior.
• Add a regression test using a real temporary Git repository with two commits and no tags.

Fixes #186

Validation

• The new regression test failed before the fix with 0 == 2; it now includes both commits and passes.
• npm test: 62 passed, 0 failed; statement, branch, function, and line coverage all remain 100%.
• npm run lint: passed.
• git diff --check: passed.

No npm package was published and no GitHub release was created during local validation.

[Jason10191019999]

The previous failure on Node 22 / windows-latest was not a test assertion: the node:test runner aborted test\command-publish.test.js with Unable to deserialize cloned data due to invalid or unsupported version. (ERR_TEST_FAILURE from the runner's IPC), which then cascaded into the 100% coverage threshold error. The full suite passes locally on Windows with 100% coverage, and all other matrix jobs passed. I've pushed an empty commit to retrigger CI — could a maintainer approve the pending workflow run? Thanks!