Grid Versioning

All LyteNyte Grid packages follow semver versioning. A LyteNyte Grid version consists of three numbers separated by periods, such as 1.2.0.

Each number in a version corresponds to a specific type of release (major.minor.patch):

• Major: Indicates incompatible changes that break backward compatibility. Adopting a new major version may require code changes in your application.

• Minor: Represents compatible changes and new features that maintain backward compatibility. These versions work with your existing code without requiring modifications.

• Patch: Denotes releases containing bug fixes and minor improvements.

We commonly refer to minor and patch releases as updates, while major releases are considered upgrades.

Release Cadence

LyteNyte Grid does not follow a fixed release schedule. Bug fixes are released as soon as they pass all internal checks and testing procedures.

While major releases with new capabilities may seem desirable, we recognize that developers prefer stability and minimal code changes. With this in mind, 1771 Technologies strives to minimize or completely eliminate breaking changes. Most feature improvements are delivered as compatible minor updates.

Checking for the Latest Version

The current version is displayed on our documentation site below the navigation bar. If you're reading this guide on our website, you can check there directly.

Alternatively, you can verify the latest published version on the NPM Registry.

Version Date

For Enterprise license holders, your license covers all versions released within your license term (typically one year from purchase date). If you use a version of LyteNyte Grid outside your license term, a watermark will appear in your application.

LyteNyte Grid exports both the version number and version date for reference:

import { versionDate, version } from "@1771technologies/lytenyte-pro";