Important Notice: Transitioning to Date-Based Versioning for NX POS 🗓️🚀

To improve deployment tracking and provide absolute clarity for our engineering teams, certified installation technicians, and venue managers, NX Restaurant is officially retiring semantic versioning. Beginning with our next release cycle, the platform will migrate to an industry-standard date-based versioning convention.

🔍 The New Versioning Structure

Moving forward, all platform builds, terminal APKs, and portal configurations will utilize a strict YY.MM.DD format. This structure directly translates to the exact calendar date the release was finalized:

Version Format:
YY.MM.DD

YY: Two-digit calendar year (e.g., 26 for 2026)
MM: Two-digit month indicator (e.g., 06 for June)
DD: Two-digit calendar day of the release (e.g., 09 for the 9th day)

Example: A build deployed on June 9, 2026, will be explicitly designated as version 26.06.09. This completely replaces old incremental sequencing strings (such as v1.6.3-build4).

🛠️ Release Frequency and Safety Guards

This change is designed to eliminate pipeline confusion when cross-referencing field bugs with active codebranches. To maintain absolute consistency:

Single-Day Release Cap: The deployment engine enforces a strict cap of one public production version per calendar day.
Deterministic Ordering: By shifting to dates, any field technician can instantly determine if a terminal is running outdated software simply by looking at the device info string—no release matrix required.

📢 Monthly Feature Announcements

To align with this new release train, we are adjusting our partner enablement cadence. During our standard Monthly NX Partner Webinar, the product management team will detail the feature roadmap and technical deliverables for the upcoming milestone version month.

Example: The upcoming May webinar will comprehensively cover all capabilities slated for the 26.06 branch (the June 2026 releases).

Technical Impacts for Developers and Integrators 💻

If you manage third-party API hooks, automated deployment scripts, or parse the device state log tables, update your systems to accommodate the structural change:

JSON

/* Legacy Format Parse (Retired) */
{
  "nxPosAppVersion": "1.6.3"
}

/* New Standard Format Parse (Enforced) */
{
  "nxPosAppVersion": "26.06.09"
}

String Parsing Validation: Ensure your internal diagnostics tools handle decimal-separated integers where the leading index values map to higher numerical boundaries than semantic majors (e.g., 26 vs 1).
Loggly & Firehose Queries: Update your saved search patterns to filter by the new date-based wildcards when isolating specific regional terminal updates.

Questions regarding the transition? Please submit a technical inquiry ticket through the Partner Portal or prepare your questions for the open Q&A session at this month's upcoming partner webinar. 🆘✨