From the course: LLMOps in Practice: A Deep Dive

Unlock the full course today

Join today to access over 24,900 courses taught by industry experts.

Version management

Version management

So now let's switch gears to the third part of the ops implementation for our server. And that's versioning. Versioning is, of course, very easy to do. Whenever you change or update something, you can change the version number, but it's also very easy to become inconsistent. If you're currently at version 1.0.1 and you change something, does it become 1.0.2 or maybe 1.1.1 or maybe 2.0? Well, who knows? So to take some of the subjectivity out of this, a technique using semantic versioning can be adopted. And when that's backed up by a library, which helps you have some discipline about your versioning and which allows you to set that versioning in a way that the app can be version-aware, you can now begin to have a clear versioning strategy. And to use this, you're going to create a new file and give it a meaningful name like version.js. This file will use a configuration file, maybe version.json to store the version number and metadata about any changes. Version.js will export two…

Contents