Update procedure for changed variables

What is the intended way to update a project in case of a changed variable in .cruft.json? Looks like a feature for this is missing because only the git commit is checked, not changes in this file.

[benlindsay]

Cruft looks like an awesome tool, thanks for building it! Being able to change variables whether or not the template has changed would be a great feature, and one that copier does. From my perspective, if this could be implemented in cruft, then all the main features I like about copier would be available to cookiecutter.

[brisberg]

I think I see what @languitar is getting at: It would be nice to be able to alter cruft variables and apply the generated diff even if the template is currently up to date.

Example:

I feel I am ready to put out a new release for projectFoo which is currently on v1.0.0. Before I do so I want to grab the latest cruft boilerplate and make sure it works correctly.

cruft update
yarn test
git add .
git commit -m "Cruft Updates"

Now it is time for a version bump and then a release:

cruft update -i
# Alter the 'version' cruft variable to `1.1.0`
git add .
git commit -m "Release v1.1.0"
git tag v1.1.0

As it stands this workflow is not possible because after the first cruft update the project and template are in-sync and cruft update -i will not re-trigger the variable prompt.

---

Is there currently an update mechanism to make this workflow possible?