You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
changelogen uses external tool pkg-types, that does nothing special, just 1 line to be honest. And that leads to undesired behavior when the last line removes
Additional context
I've just noticed that changelogen uses pkg-types which ignores the use case when eol-last preferred. You maybe already noticed that changelogen "removes" last line in package.json because relies on external util, which doesn't care about user preferences
I think that this is an important issue, since it's requires for end user to change eslint rules.
Possible solution: wait for implementation of unjs/changelogen#130 which will allow to release without version changing and hence must not override package.json file
Desired solution: change version inplace instead of overriding whole file
Logs
No response
The text was updated successfully, but these errors were encountered:
Environment
Not involved
Reproduction
Steps to reproduce
package.json
changelogen --release
commandExpected
Changes in the version line only
Actual
Last line removed
Describe the bug
changelogen
uses external toolpkg-types
, that does nothing special, just 1 line to be honest. And that leads to undesired behavior when the last line removesAdditional context
I've just noticed that
changelogen
usespkg-types
which ignores the use case wheneol-last
preferred. You maybe already noticed thatchangelogen
"removes" last line inpackage.json
because relies on external util, which doesn't care about user preferencesI think that this is an important issue, since it's requires for end user to change eslint rules.
Possible solution: wait for implementation of unjs/changelogen#130 which will allow to release without version changing and hence must not override
package.json
fileDesired solution: change version inplace instead of overriding whole file
Logs
No response
The text was updated successfully, but these errors were encountered: