inconsistent changelog: empty or not (random)

Question

inconsistent changelog: empty or not (random)

slorber opened this issue 4 years ago · comments

Sébastien Lorber commented 4 years ago

Hi,

I'm working on docusaurus. We are long-time lerna-changelog users.

I noticed that Lerna gives me unpredictable changelogs.

A command can give me an empty changelog, and 10 seconds later, the exact same command gives me the changelog I want:

As I'm not able to enable verbose logging or whatever, I don't really know what is happening.

I noticed that when the changelog is empty, the last % of the progress bar takes much longer just before.

Also noticed that running lerna-changelog --from lastReleaseTag is much faster than just lerna-changelog, and much more likely to give me a non-empty output. Basically, I feel

Has anyone an idea about what is going on?

I tried to delete the .changelog generated folder to see if it improves, but not really. Maybe there's some rate-limiting happening and errors are swallowed or something?

The repo is public and my token has the correct permissions, afaik:

Tobias Bieniek · Answer 1 · Wed Jul 29 2020 23:42:01 GMT+0800 (China Standard Time)

hmm, thanks for reporting this. I haven't noticed any such issues so far unfortunately

As I'm not able to enable verbose logging or whatever, I don't really know what is happening.

yeah, I guess we could/should introduce something like https://github.com/visionmedia/debug to enable verbose logging if such things happen 🤔

Sébastien Lorber · Answer 2 · Thu Jul 30 2020 00:07:55 GMT+0800 (China Standard Time)

Yes that could be helpful.

For example, just logging which tag it uses when I don't provide --from attribute would be nice

Sébastien Lorber · Answer 3 · Sat Aug 01 2020 18:12:22 GMT+0800 (China Standard Time)

FYI I tried with a new Github token and it didn't work better :'(

Izel Nakri | izelnakri.eth · Answer 4 · Sun Dec 06 2020 19:56:46 GMT+0800 (China Standard Time)

@Turbo87 I have the sample problem, lerna-changelog shows the progress bar and then silently fails(succeeds) without creating a CHANGELOG, lerna-changelog --from lastReleaseTag doesnt help either, it silently fails on all cases. You can try it here, we should probably make lerna-changelog more strict so it never fails silently.

https://github.com/izelnakri/memserver [having the CHANGELOG or not having has no impact on the command output, tried that as well]

Tobias Bieniek · Answer 5 · Sun Dec 06 2020 20:06:37 GMT+0800 (China Standard Time)

@izelnakri the PRs in your project don't have any labels, which is why they don't show up in the generated changelog. see https://github.com/lerna/lerna-changelog#usage

Izel Nakri | izelnakri.eth · Answer 6 · Sun Dec 06 2020 20:52:02 GMT+0800 (China Standard Time)

Yes, I just realized that after an hour of debugging 🤦 Added an explanation PR here: #391

Initially I thought it autogenerates a label for each commit by default if missing, my assumption was wrong 😄 It would be nice I think if we build some 'AI' like logic to generate changelog per PR if its missing label :)