forked from conventional-changelog/standard-version
-
Notifications
You must be signed in to change notification settings - Fork 49
Open
Labels
bugSomething isn't workingSomething isn't working
Description
Describe the bug
- The dependency
[email protected]creates a CPS-styletransformfunction (never returns, callscb(null, commit)) - The dependency
[email protected]tries to use it in a non-CPS style (commit = transform(commit, context), resulting incommitbeing null) - The result is that an empty array of
commitsis given to the CHANGELOG.md generator, and that returns
## [0.0.221](https://github.com/AUTHOR/REPO/compare/v0.0.220...v0.0.221) (2024-11-26)
without any commits listed.
Current behavior
No commits are listed in the generated CHANGELOG.md
Expected behavior
Commits are listed in the generated CHANGELOG.md
Environment
commit-and-tag-versionversion(s):12.5.0- Node/npm version: Node v20.18.1, NPM v10.8.2
- OS: Ubuntu 22.04.5 LTS (Github Actions runner)
Possible Solution
Hopefully updating conventional-changelog to something new-ish (currently used version is 4.0.0 while the newest version seems to be 6.0.0 according to npmjs.com) would help? I haven't tried this.
Looking at the current master version of conventional-changelog:
corestill uses CPS in mergeConfigwriterhas been substantially rewritten and the closest code seems to be here, though it looks like it has the same bug. Maybe I'm missing some promisification happening elsewhere.
Additional context
I'm using commit-and-tag-version from within [email protected]. It lists
"commit-and-tag-version": "^12",
as a dependency automatically for all TS projects.
KristjanESPERANTO
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working