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
It would be great if we could specify a file to have the version bumped instead of using package.json
For example: I have an angular app running inside docker. However, to build it we need to install all the dependencies on package.json, the thing is these dependencies doesn't change in every deployment. But because standard-release bump the version of package.json file, docker can not benefit from the cache.
It would be great if instead we could specify a version file, so we could benefit from automatic versioning and also from docker caching.
The text was updated successfully, but these errors were encountered:
Or even specify multiple package.json files to modify. For example, I have a subpackage that I'd like to keep in sync with the main version. I'm looking into workarounds for this and haven't found a clean/simple implementation yet.
Just noticed #225 and realized maybe lerna is the right solution for multiple files? Personally I think that addition wouldn't be too bad here but I understand not wanting to muddy the scope for standard-version if you want to keep it more focused on simple one-package projects.
It would be great if we could specify a file to have the version bumped instead of using package.json
For example: I have an angular app running inside docker. However, to build it we need to install all the dependencies on package.json, the thing is these dependencies doesn't change in every deployment. But because standard-release bump the version of package.json file, docker can not benefit from the cache.
It would be great if instead we could specify a version file, so we could benefit from automatic versioning and also from docker caching.
The text was updated successfully, but these errors were encountered: