bug: initial generated changelog includes every package commit in monorepo

[jrson83]

Description

When using sparkee the first time in a monorepo to publish a package which already has git-tags and no changelog, sparkee generates a changelog which includes EVERY commit that has been made to the package, since the creation of the git-repository.

Example

See the savescum repo.

Here is what I did:

1. I created the tag savescum@0.1.0 and published to npm and pushed the release.
2. I made two commits to the savescum package:

• fix(savescum): add function to resolve workspace root closes
• fix(savescum): move web package to dependencies

3. I used sparkee to publish savescum@0.1.1 and generate a changelog.
4. The changelog includes every commit made to the package in the changelog.

Expected result

Sparkee should only include a range of commits made between the two releases of v0.1.0 and v0.1.1.