Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Being able to choose file to bump version #432

Open
tbnovaes opened this issue Aug 9, 2019 · 5 comments
Open

Being able to choose file to bump version #432

tbnovaes opened this issue Aug 9, 2019 · 5 comments

Comments

@tbnovaes
Copy link

tbnovaes commented Aug 9, 2019

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.

@bcoe
Copy link
Member

bcoe commented Aug 19, 2019

@jbottigliero does this mesh with some of the work you've been doing related to supporting bumping the version of arbitrary file types?

@skipjack
Copy link

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.

@skipjack
Copy link

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.

@jbottigliero
Copy link
Member

Hey All,

Yes - it sounds like this should be resolved by #372

@jbottigliero jbottigliero self-assigned this Aug 24, 2019
@jbottigliero
Copy link
Member

This change has landed in master and will be included in the next major release – see the README for details.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

4 participants