User Portal - Docs
GitHubWebsiteToggle Dark/Light/Auto modeToggle Dark/Light/Auto modeToggle Dark/Light/Auto modeBack to homepage

Releases

This document outlines our practices for delivering a cutting-edge application development platform that maintains stability. We aim to introduce future changes predictably, ensuring that everyone who relies on User Portal is informed about the timing and nature of new features, and prepared for the removal of outdated ones.

Versioning

Version numbers indicate the level of changes that are introduced by the release. This use of semantic versioning helps you understand the potential impact of updating to a new version.

A version number has three parts: major.minor.patch. For example, version 1.2.0 indicates major version 1, minor version 2, and patch level 0.

The version number is incremented based on the level of change included in the release.

LEVEL OF CHANGEDETAILS
Major releaseContains significant new features, some but minimal developer assistance is expected during the update. When updating to a new major release, you might need to run update scripts, refactor code, run additional tests, and learn new APIs.
Minor releaseContains new smaller features. Minor releases are fully backward-compatible; no developer assistance is expected during update, but you can optionally modify your applications and libraries to begin using new APIs, features, and capabilities that were added in the release. We update peer dependencies in minor versions by expanding the supported versions, but we do not require projects to update these dependencies.
Patch releaseLow risk, bug fix release. No developer assistance is expected during update.

Release frequency

We work toward a regular schedule of releases, but in general, expect the following release cycle:

  • A major release when big features are introduced.
  • A minor release on every GDI milestone.
  • A patch release and pre-release on every change / bugfix introduced into a minor release.

Releases

VersionStatusReleased at
^v1.3IN DEVELOPEMENTPlanned to October 2024
^v1.2RELEASEDJune 2024
^v1.1We aligned all components versions to the same {major}.{minor}, what led us to skip this versionN/A
^v1.0RELEASEDJanuary 2024

Changelogs