Not updating changes of package.json or CHANGELOG.md #1781
-
Dependencies:
IssueNeither the I am using GitHub Actions, I tested initially with the the |
Beta Was this translation helpful? Give feedback.
Replies: 7 comments 2 replies
-
please include the debug logs from your CI run |
Beta Was this translation helpful? Give feedback.
-
Sure @travi
|
Beta Was this translation helpful? Give feedback.
-
I see no evidence of the git plug-in being loaded in your output. That also does not look like debug logging, even though you have the flash enabled in your config. My best is that your config is not being loaded at all. Could you confirm the spelling of the filename, it's location and structure? It may be helpful to use the debug flag directly in the cli command to get full details. |
Beta Was this translation helpful? Give feedback.
-
Sure The file is located on the root of the repository, the filename is I have been following this tutorial as it saw it was good, https://kevinkreuzer.medium.com/the-way-to-fully-automated-releases-in-open-source-projects-44c015f38fd6 and I forked the repository from the tutorial and did not make any changes, even though appears to be working on the main repository on my repository which is exactly the same is not working https://github.com/juancarlosjr97/node-command-line-starter. I ran from my local using
This is my file structure
I hope that would be useful @travi. Thank you very much. |
Beta Was this translation helpful? Give feedback.
-
@travi I noticed is not picking up |
Beta Was this translation helpful? Give feedback.
-
i also notice the following in your logs above:
rather than saying it is loading the config from your |
Beta Was this translation helpful? Give feedback.
-
i'm going to move this into a discussion, since that is where we are hoping to direct support discussions like this one going forward |
Beta Was this translation helpful? Give feedback.
i also notice the following in your logs above:
rather than saying it is loading the config from your
.releaserc
. it doesnt look like it from the project you linked to, but is it possible that you have arelease
property defined in yourpackage.json
that would be taking precedence over the.releaserc
?