Releasing from alternate path fails to find prior release

[bcoe]

When releasing from alternate path, with --monorepo-tags, v13 of release-please fails to find prior release, resulting in bad release proposal, see:

conventional-changelog/conventional-changelog#874

Reproducing

node ./build/src/bin/release-please.js release-pr --release-type=node --token=$GITHUB_TOKEN --path=packages/conventional-changelog-cli --monorepo-tags --package-name=conventional-changelog-cli --repo-url=conventional-changelog/conventional-changelog --dry-run

Expected Output

Ideally we'd be able to bootstrap the library based on the prior tags, or based on a manifest?

[bcoe]

@chingor13 update, I've tried creating an initial release tagged to an earlier point in history, which did not work:

https://github.com/conventional-changelog/conventional-changelog/releases/tag/conventional-changelog-cli-v2.2.1

I also tried creating a branch with the appropriate naming convention:

https://github.com/conventional-changelog/conventional-changelog/tree/release-please--branches--master--components--conventional-changelog-cli

And finally, adding a manifest with a bootstrap sha:

https://github.com/conventional-changelog/conventional-changelog/blob/master/release-please-config.json

In all cases it fails to find a working set of commits for the conventional-changelog-cli submodule.