5 ms·

Meta question: why are we at v350.06680? The numbers nerd in me needs to understand.

• holler 6y ago
  haha! tbh I needed _something_ to be able to track versions for debugging purposes once I had some real users, and I ended up just using the client `v${commit number}.{last 5 commit hash}` Hope that answers it! thank you for checking out sqwok & have a nice day
  • jen729w 6y ago
    It does, thanks. I’ve always wondered, how does the commit hash get in to the actual version number? You don’t know the hash before you commit, so now to get the hash in to the public commit version you have to commit again, which changes the hash!
    • allenu 6y ago
      I'm guessing the build/deploy stage sets that up in the environment, so it's not actually committed in the repo.
      • holler 6y ago
        yep that's it, it's created in the build stage and passed into the app!
• jan6 6y ago
  uninformed guess: every commit is a version bump, every push to master is a major version bump?