# 2027.X Versioning Questions

**URL:** <https://forum.inductiveautomation.com/t/2027-x-versioning-questions/117765>\
**Category:** Ignition 2027 Early Access\
**Created:** [November 5, 2026, 11:14pm UTC](https://forum.inductiveautomation.com/t/2027-x-versioning-questions/117765 "2026-11-05T23:14:57Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![bmusson](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bmusson/32/87530_2.png) [@bmusson](https://forum.inductiveautomation.com/u/bmusson)\
**Post date:** [November 5, 2026, 11:14pm UTC](https://forum.inductiveautomation.com/t/2027-x-versioning-questions/117765/1 "2026-11-05T23:14:57Z")

</div>

I'm getting ready to start branching Embr for 2027 support, and I've got some questions WRT versioning, mostly around this statement:

> [@Introducing Ignition 2027, Packed With AI, Charting, and Historian Upgrades](https://forum.inductiveautomation.com/t/introducing-ignition-2027-packed-with-ai-charting-and-historian-upgrades/117728/1):
>
> Ignition 8.3 remains fully supported as an LTS release through September 2030, and the next LTS designation will land with Ignition 2027.15.0-LTS in Q1 2028

1. Does 2027.15.0 imply a March 2028 release of Ignition 2027?

2. What's the expected relationship between the last 2027.2 release and the first 2027.15 release?

3. Should I expect a module compiled against 2027.2.X to work against 2027.15.Y?  
Or are 2027.2, 2027.15, and (2027+?).Z going to be totally different targets?

Basically I'm trying to decipher if my build target should be simply **2027** , or if I need specifically target **2027.2**.

(Also I know things may change... a current vibes-based answer would be good enough 😆)

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [November 5, 2026, 11:25pm UTC](https://forum.inductiveautomation.com/t/2027-x-versioning-questions/117765/2 "2026-11-05T23:25:12Z")

</div>

The _plan_ is that the `major.minor` tuple we previously used as the major version (e.g. `8.1`, `7.9`, `8.3`) is collapsed into the `major` field, as in, the **API stability** layer is `2027`. Every release of `2027` should have the same SDK/API contract (again, possibly barring the AI-specific things mentioned in the other thread).

> [@bmusson](#):
>
> 1. Does 2027.15.0 imply a March 2028 release of Ignition 2027?

Yes, plus/minus a few weeks.

> [@bmusson](#):
>
> 1. What's the expected relationship between the last 2027.2 release and the first 2027.15 release?

I'm not sure what you're asking here.

---

<div class="post-metadata">

**Author:** ![bmusson](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bmusson/32/87530_2.png) [@bmusson](https://forum.inductiveautomation.com/u/bmusson)\
**Post date:** [November 5, 2026, 11:38pm UTC](https://forum.inductiveautomation.com/t/2027-x-versioning-questions/117765/3 "2026-11-05T23:38:45Z")

</div>

Great, this is what I was hoping for 😁

> [@paul-griffith](#):
>
> I'm not sure what you're asking here.

Basically asking if **2027.2** and **2027.15** would have the same API level.  
Same question, just framed a little different.

So if I'm understanding correctly:  
If I have targets for `8.1`, `8.3`, and `2027`, when `2027.15` is released as an LTS, it'll be the same SDK API contract as `2027.2`.

(ignoring the AI-specific asterisks, which I'm not super worried about ATM).

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [November 5, 2026, 11:43pm UTC](https://forum.inductiveautomation.com/t/2027-x-versioning-questions/117765/4 "2026-11-05T23:43:31Z")

</div>

Yep, that's the intention.  
Moving to a new yearly release consistently intentionally allows us to make API breaking changes on a regular cadence, so that we're not doing the thing we've done in the past where we try to "cram" a bunch of stuff in to the next major release because that's our option to make breaking changes. Now that there's a...mega? release train, you get what you get.

---

<div class="post-metadata">

**Author:** ![michael.flagler](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/michael.flagler/32/26272_2.png) [@michael.flagler](https://forum.inductiveautomation.com/u/michael.flagler)\
**Post date:** [November 6, 2026, 4:52am UTC](https://forum.inductiveautomation.com/t/2027-x-versioning-questions/117765/5 "2026-11-06T04:52:54Z")

</div>

Then once 2027.15.0 is released, will only the patch number update until it's no longer supported or will it still follow months since the year it was originally released.

Are minor versions going to be released every month? (I feel like this was covered at ICC but I've slept since then)

Are the patch numbers going to be for things like fixing regressions between minor versions so then we may not have a patch version other then 0 sometimes not probably never reach 50+ again.

---

<div class="post-metadata">

**Author:** ![Pdeswert](https://avatars.discourse-cdn.com/v4/letter/p/a8b319/32.png) [@Pdeswert](https://forum.inductiveautomation.com/u/Pdeswert)\
**Post date:** [November 6, 2026, 10:03am UTC](https://forum.inductiveautomation.com/t/2027-x-versioning-questions/117765/6 "2026-11-06T10:03:40Z")

</div>

So basically, every year:

- New release with the year of release as it version number
- Previous years release is branded as LTS

?

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [November 6, 2026, 2:13pm UTC](https://forum.inductiveautomation.com/t/2027-x-versioning-questions/117765/7 "2026-11-06T14:13:29Z")

</div>

> [@Pdeswert](#):
>
> - Previous years release is branded as LTS

Every other year.

The branch starting with 2027.2 will become LTS when the branch starting with 2028.2 is released. Then 2029.2 will become LTS when 2030.2 is released.

---

<div class="post-metadata">

**Author:** ![KathyApplebaum](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kathyapplebaum/32/7261_2.png) [@KathyApplebaum](https://forum.inductiveautomation.com/u/KathyApplebaum)\
**Post date:** [November 6, 2026, 5:12pm UTC](https://forum.inductiveautomation.com/t/2027-x-versioning-questions/117765/8 "2026-11-06T17:12:45Z")

</div>

> [@michael.flagler](#):
>
> Are minor versions going to be released every month?

Every other month.
