Closed christianacca closed 6 years ago
Also, by calculating the fingerprint from the previous version of the module, you do not have to commit the fingerprint file into source control
FYI, just trying out my proposed solution. If it works I'll send a PR
PR with my proposed solution: https://github.com/KevinMarquette/PlasterTemplates/pull/34
Also a nice by-product is that the fingerprint file no longer needs to be checked into git
Related to https://github.com/KevinMarquette/PlasterTemplates/issues/4
Been looking at the fingerprint logic and I think there is non-obvious implication to how it works (please correct me if I'm wrong). Most of the time the logic will miss feature changes and bump the patch version instead.
Take the following typical scenario...
Possible solutions
1. Commit fingerprint only after a deploy
That's a pain to remember.
2. Generate the fingerprint from the previous version of the module
To really fix this, the calculation logic needs to install the previous version of the module, generating a fingerprint from this. It can then compare this with a fingerprint calculated from the current module.
The trick would be:
Save-Module
rather than install module to get the previous version of the module onto disk