At IMGENAI, we’re constantly evolving our SaaS platform to bring you more powerful features, stronger performance, and better user experiences. As part of that commitment, we follow a structured versioning policy to keep our updates transparent, predictable, and reliable for your teams.
Here’s how it works.
🔢 Our Versioning Format
We use Semantic Versioning, a widely adopted standard that follows this format:
MAJOR.MINOR.PATCH
Each number tells a different story:
MAJOR: Big, breaking changes that may require action on your side
MINOR: New features that don’t disrupt your current setup
PATCH: Bug fixes, performance improvements, and behind-the-scenes updates
Example:
A version number like 2.4.1 means:
2 = Major version (some breaking changes may have occurred previously),
4 = Four feature updates since version 2.0,
1 = One patch applied since the last feature release.
✅ What Triggers Each Type of Update?
Version Type | Trigger | Will You Need to Take Action? |
PATCH | Bug fixes, small UI adjustments, or performance/security improvements | ❌ No |
MINOR | New features, enhancements, or improvements that don’t affect existing functionality | ❌ No |
MAJOR | Changes that break or replace existing functionality (e.g., new API structure) | ✅ Possibly |
We design most of our updates to be backward-compatible, so you won’t need to worry about constant rework.
🧪 For Our API Users
If you’re integrating our APIs into your systems, you’ll notice our major API versions are clearly indicated:
REST: /api/v1/your-endpoint
This makes it easy for you to adopt new functionality on your own timeline, without disruption to existing workflows.
📦 Continuous Delivery, Carefully Managed
Because we follow a continuous delivery model, we roll out PATCH and MINOR versions frequently. But we don’t believe in surprises — that’s why we:
Announce all MAJOR changes well in advance.
Use feature flags to control the rollout of sensitive updates.
Maintain a changelog so you can always track what’s new.
🗓️ What This Means for You
Stability: You can trust that your existing features will keep working.
Visibility: You’ll always know what’s changed and why.
Control: You’ll never be forced to adapt overnight — especially when it comes to APIs.
💬 Want to Learn More?
If you’re curious about an update, have feedback, or want a preview of what’s coming, our team is always happy to connect. Just reach out via contact@ar-go.co or through your customer portal.
