We've made substantial design, code, and architectural improvements with LUCI 2.0. However, if you still need to reference original assets you can do so at the LUCI 1.0 archive.
LUCI 2.0 uses a different namespace for class names, which is more aptly name
The change in class names allows us to remove any dependency from LUCI 1.0 and not introduce regression as we update and maintain LUCI 2.0. In theory, your team could support both versions as a result. For example, if you wanted to use the LUCI 2.0 button styles and use the property bar available in LUCI 1.0, you can update your buttons with the class name
Each update to LUCI follows the Semantic Versioning process, which is a set of rules and requirements that dictate how version numbers are assigned and incremented based on a major, minor, or patch to the LUCI project.
Patch version Z (x.y.Z | x > 0) is incremented when backwards compatible bug fixes are introduced. A bug fix is defined as an internal change that fixes incorrect behavior.
Minor version Y (x.Y.z | x > 0) is incremented if new, backwards compatible functionality is introduced. It is also incremented if any functionality is marked as deprecated.
Major version X (X.y.z | X > 0) is incremented if any backwards incompatible changes are introduced.
If using NPM (recommended), run:
npm update @netapp/luci --save from the root of your project.
If using compiled assets: download the latest zip files.