Manifest release stuck in release-loop with the same commits in the changelog when absolute changelog-path is specified #2329
Labels
priority: p2
Moderately-important priority. Fix may not be included in next release.
type: bug
Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Environment details
release-please
version: 16.12.0Steps to reproduce
I have a large monorepo, with releasable unit being a generated code. The structure basically looks like this:
/base/Agent
/overwrites/Agent
/generated/Agent[this is releasable and an output of base x overwrites]
(where Agent is one of the packages)
I don't want to keep the CHANGELOG.md in the generated directory because, well, it's always deleted and recreated from scratch, and there's a different automatically generated changelog being created there, that shows the API differences between the versions.
If I specify the absolute path to the CHANGELOG in the manifest to a new directory
/changelogs/Agent/CHANGELOG.md
the CHANGELOG is kept, but the release-please goes into a infinite loop
This is is the resulting changelog:
This is the top of branch history:
This is the .release-please-manifest.json that only release-please writes to:
And the config:
Is there a special release-type or another way to preserve the CHANGELOG in a directory different than the package?
The text was updated successfully, but these errors were encountered: