Tagging and Releasing Software Versions
Every release of your software is given a version number and a tag — a permanent marker in the code's history. This lets everyone refer to a precise, known state of the product.
Clear versioning underpins reliable rollbacks, support and communication about what changed.
How Version Numbers Work
We commonly use semantic versioning, written as three numbers such as 2.4.1. Each part signals the kind of change in the release, so the number itself communicates how significant an update is.
- Major (the first number): a big change that may need attention.
- Minor (the second): new features, safely added.
- Patch (the third): small fixes and tweaks.
Why Tags Are Valuable
A tag lets us recreate the exact code behind any release, which is essential for diagnosing an issue or rolling back. It also gives us a clean way to describe what each release contained in your release notes.
Clear versioning is also the foundation of good support conversations. When you report something, knowing exactly which version you are on lets us reproduce the situation precisely rather than guessing at what is running.
Frequently Asked Questions
Do I need to understand version numbers?
Not in detail. They are mainly for the team, but the pattern lets you tell at a glance whether a release is a big change or a small fix.
If you need a hand with any of this, your Progressive Robot delivery team is ready to help. Raise a ticket from the Support area of your client portal or speak to your account manager and we will guide you through the next steps.