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
Describe the bug
It seems so that I'm not able to hand the same structure into the command line arg --bumpFiles as by using the .versionrc file.
Current behavior
running commit-and-tag-version --bumpFiles "[{\"filename\":\"custom-bump-file.md\",\"updater\":\"custom-updater.js\"}]"
succeeds but without updating the custom-bump-file.md and with instead saying:
Unable to obtain updater for: "[{\"filename\":\"custom-bump-file.md\",\"updater\":\"custom-updater.js\"}]"
- Error: Unsupported file ([{"filename":"custom-bump-file.md","updater":"custom-updater.js"}]) provided for bumping.
Expected behavior
I would like the command line arg to be able to work with the same input as the .versionrc file
Environment
commit-and-tag-version version(s): 10.1.0
Node/npm version: Node v18.7.0 / npm 8.15.0
OS: macOS Monterey 12.5
Possible Solution
I'm guessing the command line arg is not parsed/interpreted as a json object?
Additional context
Why am I not just use the .versionrc file: I would like to call the commit-and-tag-version tool multiple times with different configuration for which additional files (besides the CHANGELOG.md) to update. For that I would like to just hand over the different configuration using the --bumpFiles command line arg.
The text was updated successfully, but these errors were encountered:
Thanks for the detailed report! You are correct that the way the config is parsed is different depending on how it is invoked.
I'd quite like to fix this - there's a little bit of context on #31, but basically what needs to happen is to generalise the configuration structure so that the source doesn't matter. It's a medium amount of effort, but something that would be a substantial improvement.
hi @TimothyJones
since I'm working on a new setup and ended up at the same problem as here I wanted to ask if there are any updates about generalising the configuration? 🙂
To solve this issue back then I used something very ..., lets say not preferred 😅 (its called patch-package and I'm not proud of using it)
Describe the bug
It seems so that I'm not able to hand the same structure into the command line arg
--bumpFiles
as by using the.versionrc
file.Current behavior
running
commit-and-tag-version --bumpFiles "[{\"filename\":\"custom-bump-file.md\",\"updater\":\"custom-updater.js\"}]"
succeeds but without updating the
custom-bump-file.md
and with instead saying:Expected behavior
I would like the command line arg to be able to work with the same input as the
.versionrc
fileEnvironment
commit-and-tag-version
version(s): 10.1.0Possible Solution
I'm guessing the command line arg is not parsed/interpreted as a json object?
Additional context
Why am I not just use the
.versionrc
file: I would like to call the commit-and-tag-version tool multiple times with different configuration for which additional files (besides the CHANGELOG.md) to update. For that I would like to just hand over the different configuration using the --bumpFiles command line arg.The text was updated successfully, but these errors were encountered: