Handling request failures when build number is obtained from GitHub

[NBTX]

Per discussion in #121, this issue is to determine what we should do if we can't get the latest build number from GitHub at build time. The options I can think of are as follows:

1. Hide the name section in the version information.
2. Use 'deep clone' on Travis and get the tag from the git history. (Could make builds slower over time but probably wouldn't have that big an impact)
3. Get it from package.json but make sure the value in package.json stays up-to-date. (Perhaps use GitHub Actions or something to automatically change it to the version number in GitHub releases?) - Overall this is my preferred option.

/CC: @larouxn @liyasthomas

[liyasthomas]

I vote for updating version number from package.json
This seems the correct way to handle this, it also helps in tags as well.

Lets hear from @larouxn as well

[NBTX]

Actually funny thing, I decided 2 was my favorite option but then I came up with 3 because I wanted to put 3 things instead of 2 lol.
So thinking about it, I also prefer 3.

[larouxn]

We should keep package.json version up to date anyway. So, if a solution for build numbers also ensures that, then that's a double win. 🙌

[NBTX]

Exactly! ^
Guess I'll get working on 3 then haha

[liyasthomas]

@NBTX this issue seems to be absolute. Would you mind closing it?

[NBTX]

@liyasthomas absolute?

[liyasthomas]

Sorry. Oftentimes, version number is still fetched from package.json causing version tag without "v" before the tag. This issue is persisting.

[liyasthomas]

Now the version number is correctly fetching from package.json and release tag, so I think I should this issue.