Release note

Versioning Scheme

The package use a three-part numbering system (e.g., 1.2.3) to track updates. This helps the developers to understand the scope of changes at a glance.

The "Patch" Release (0.0.X)

The third digit is reserved for small fixes.

• Purpose: Bug fixes, security patches, or minor text corrections.
• Impact: These updates do not change how the site functions and are safe to deploy immediately.
• Example: Moving from 1.0.1 to 1.0.2.

The "Minor" Release (0.X.0)

The second digit represents medium-sized updates.

• Purpose: Adding new features or making significant modifications to existing ones.
• Impact: These introduce new functionality but remain backward-compatible (they should not "break" the existing setup !).
• Example: Moving from 1.1.0 to 1.2.0.

The "Major" Release (X.0.0)

The first digit indicates major structural changes.

• Purpose: Complete redesigns, total code refactoring, or breaking changes that alter how the system works fundamentally.
• Impact: These are significant milestones and often require thorough testing before deployment.
• Example: Moving from 1.0.0 to 2.0.0.

GIT branches

The package supports the current version and one previous version. Here the branches naming convention:

• main: Is the latest version DEV branch
• production: Is the latest version PROD branch
• support/vx.x.x : Is the legacy version PROD branches per MAJOR+MINOR release
• hotfix/vx.x.x : Is the legacy version DEV branches for PATCH release only

Support Policy

The current version of the package is construct with SCSS and vanilla JS !

Make sure you can use some of the new HTML/CSS/JS into the browser !