Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
latest release breaks changelog commit (note, this issue seems to potentially be related to dotgitignore)
See original GitHub issueerror:
$ standard-version
✔ outputting changes to CHANGELOG.md
✔ committing CHANGELOG.md
Command failed: git commit CHANGELOG.md -m "chore(release): 1.0.0"
Command failed: git commit CHANGELOG.md -m "chore(release): 1.0.0"
rolling back to 4.2.0 fixes issue
Issue Analytics
- State:
- Created 6 years ago
- Reactions:5
- Comments:25 (11 by maintainers)
Top Results From Across the Web
Extract description from CHANGELOG file with keep a ... - GitLab
Currently it is possible read description from a file, but in many cases the CHANGELOG file contains all the releases history.
Read more >dotgitignore | Yarn - Package Manager
Change Log. All notable changes to this project will be documented in this file. See standard-version for commit guidelines.
Read more >Git is not detecting a file and is not in .gitignore - Stack Overflow
Extra note, I ran into this problem and found that changes to files weren't being added to commits. Nothing seemed to work, except...
Read more >Changelog - The GitHub Blog
We just finished releasing the last feature update of the year for Projects. It was relatively light, mainly composed of bug fixes and...
Read more >dotgitignore - npm
find the closest .gitignore file, parse it, and apply ignore rules. Latest version: 2.1.0, last published: 3 years ago.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Same problem for me. In my case the package.json is included in the .gitignore, and the changelog is never outputed with the 4.3.0
Having same issue with 4.3.0, upgraded to 4.4.0 and still have same issue with:
standard-version --preset angular --release-count 0 "--release-as-patch"I receive the following error:Error is outputted twice. Rolling to 4.2.0 fixed the issue for me as well.