Git hook update package json version

Question

In our project we often forget to update version numbers in Package.json file. Ours is a AngularJS project. In our package JSON file we are specifying the below two version information

"version": "1.0.7",
"devVersion": "1.0.4"

Before Merging a branch to develop I want a automated script to update these above two version numbers. I am thinking Git Hooks will help me.

Where can i find the hooks, I am able to see the hooks in my local repo under .git folder. I am confused which hook to use. Searching on Google suggests I have to create hooks on server.

Where can i find them and can i update the above both keys (version and devVersion) ?

Pls suggest the location and hook to use, this will solve a lot of problem.

Related to https://stackoverflow.com/questions/13059991/update-package-json-version-automatically/ and https://stackoverflow.com/questions/25796533/how-can-i-place-my-meteor-apps-version-number-in-the-ui — Anima-t3d, Jul 19 '18 at 08:13

score 11 · Answer 1 · answered Jul 19 '18 at 08:11

I am using husky and git-branch-is:

"scripts": {
  ...
  "postmerge": "(git-branch-is master && npm version minor || 
  (git-branch-is dev && npm --no-git-tag-version version patch)",
  ...
},

Read more about npm version

Webpack or Vue.js

If you are using webpack or Vue.js, you can display this in the UI using Auto inject version - Webpack plugin

NUXT

In nuxt.config.js:

var WebpackAutoInject = require('webpack-auto-inject-version');

module.exports = {
  build: {
    plugins: [
      new WebpackAutoInject({
        // options
        // example:
        components: {
          InjectAsComment: false
        },
      }),
    ]
  },
}

Inside your template for example in the footer:

<p> All rights reserved © 2018 [v[AIV]{version}[/AIV]]</p>

Interesting implementation, more precise than my answer. +1 – VonC Jul 19 '18 at 08:32 — VonC, Jul 19 '18 at 08:32

score 6 · Accepted Answer · edited May 23 '17 at 12:08

You have two kinds of hooks (both present in any .git/hooks folder): server and client hooks.
They are listed in "Customizing Git - Git Hooks"

A merge is a local operation, so if you wanted to automate any process during a merge, you would need a client hook, like a post-commit hook (meaning executed just after creating a merge commit).
If you need to update that file before a merge, you can try a pre-commit hook, and check if a merge is in progress (if not, your pre-commit hook would do nothing since you want to update the versions only before a merge).

You can see in this answer an example of a post-commit hook which generates a version.json file.
If is written in node, but you can write a hook ni any scripting language you want.

Duc Trung Mai · Answer 3 · 2020-12-17T02:00:22.467

5

With Husky, it's extremely simple:

{
  "name": "demo-project",
  "version": "0.0.3",
  "husky": {
    "hooks": {
      "pre-commit": "npm --no-git-tag-version version patch && git add ."
    }
  }
}

Note: I put git add . in the end because after we update package version, we need to stage it

edited Dec 17 '20 at 02:00

answered Nov 21 '20 at 04:10

Duc Trung Mai

2,141
1
24
23

In what file am I supposed to add this? – Ruben Szekér Jun 16 '21 at 08:02
Seems that it's even more simple without Husky, because you only need (part of) the 6th line – Digital Ninja Apr 24 '22 at 21:15

Git hook update package json version

3 Answers3

Linked