Interpret BrynQ version numbers

Interpret BrynQ version numbers

Summary:
This article explains how to read BrynQ version numbers based on Semantic Versioning.

BrynQ versioning overview
Salure uses Semantic Versioning (SemVer) for its software. This helps customers understand how big a change is and what they can expect from an update.

Semantic Versioning basics

  • Version numbers have the form X.Y.Z (for example 1.10.2).

  • X – Major version: increases when there are large, non-compatible changes. This may require changes in integrations or processes.

  • Y – Minor version: increases when new features or important improvements are added that stay compatible with earlier versions.

  • Z – Patch version: increases when small, compatible bug fixes are made.

Examples of BrynQ versions

  • Example: 1.10.2

    • 1 = major release with possibly large, non-compatible changes.

    • 10 = minor release with new features or improvements.

    • 2 = patch release with bug fixes.

  • Whenever a change affects people outside the development team, the version number is updated according to SemVer rules.

How versioning supports security and stability

  • Clear version numbers make it easier to link security fixes to specific releases.

  • Patch versions often contain security improvements or small bug fixes that increase stability.

  • Minor and major versions can include new security features or architecture changes, such as improved logging or encryption, developed through the secure development process.

Procedure:

  1. When a new BrynQ release is announced, note the X.Y.Z version number.

  2. Check which part of the version has changed:

    • If X has changed, plan extra testing and review of integrations.

    • If Y has changed, review the new features and check if they fit your processes.

    • If Z has changed, check the list of fixes, especially any security updates.

  3. Update your internal documentation or change log with the new version number and date.

  4. Communicate major and minor version changes to relevant stakeholders such as system owners or integration partners.

  5. Coordinate upgrade windows with Salure if your organization has strict change management rules.

Additional Information:

  • More information about Semantic Versioning is available on the SemVer website; BrynQ follows the core ideas summarized here.

<div class="ProseMirror" id="prompt-textarea"></div></div></div></div></div></div></div></div></div></div></div>

    • Related Articles

    • Follow BrynQ secure development process

      Summary: This article explains how Salure develops BrynQ securely, from planning and coding to testing, review, and release. BrynQ secure development overview BrynQ is developed under a structured development policy based on standards such as OWASP ...

    • Use BrynQ APIs securely

      Summary: This article explains how BrynQ secures API integrations with RBAC, detailed logging, error handling, and support for central log collection. BrynQ API security overview BrynQ offers APIs that connect to HR and other systems. Security ...

    • Manage BrynQ access securely

      Summary: This article describes how SSO, RBAC, password rules, and zero-trust principles protect access to BrynQ. BrynQ access security overview Access to BrynQ is managed with strong authentication, role-based access control, and network security. ...

    • Confirm BrynQ ISO 27001 compliance

      Summary: This article summarizes Salure’s ISO 27001 certification and the main control areas that apply to BrynQ. BrynQ ISO 27001 certification overview Salure, the organization behind BrynQ, operates an Information Security Management System (ISMS) ...

    • Protect personal data in BrynQ

      Summary: This article explains how BrynQ supports GDPR-related controls such as logging, data location, incident notification, and data deletion. BrynQ data protection overview BrynQ is designed to help you protect personal data and meet legal ...