Closed Hendrix-Shen closed 8 months ago
Hm, that's interesting. With a quick glance over the code, I do not see where I could screw up with v3.3. Are you sure that the release in question was not created before mc-publish
could put its virtual hands on it?
Yes,
When I switched to 3.2, GitHub generated changelogs: Commit#ffbc4b4 Release#dev-20 But when I switched to 3.3, the logs no longer generated: Commit#e8742e2 Release#dev-21
I will look into this shortly.
I've finally tracked down the root of this problem. The generated changelog is indeed being appended to the original one as intended. However, I inadvertently override the updated version with the original one in the subsequent steps:
Should be an easy one to fix!
I tested almost the same configuration on 3.2 and 3.3 (except for the files field) and it worked fine in 3.2, but 3.3 did not generate "Full Changelog: xxx...xxx"
My test workflow config:
Did I do something wrong?