Skip to main content

Versions and quality criteria

A version is the official snapshot of your project at a specific moment — ready to publish to Wazuh. Quality criteria (quality gates) are the list of checks RuleForge runs before letting you publish. Together they protect production from broken or incomplete content.

When to create a version​

Create a version when the project content is:

  • validated with no errors;
  • tested with the project's cases;
  • reviewed (if the policy requires review);
  • ready to be delivered to Wazuh.

Versions work as history points: you can compare, roll back, and check what was published on a given date.

Version states​

  • Draft — version was created, not yet published.
  • Published — passed all criteria and was delivered to Wazuh.
  • Archived — replaced by a more recent version or marked as ended.

Quality criteria​

Your organization may require, before publishing, a combination of:

  • Zero validation errors.
  • Maximum warnings — for example, at most 5.
  • Maximum info items — for example, at most 20.
  • Minimum quality score — for example, at least 80%.
  • All test cases passing.
  • Approved review before publishing.

Criteria are defined by the project owner and apply to all members.

Step by step​

  1. In the project, click New version.
  2. Confirm the content validated and regression is clean.
  3. If the policy requires review, confirm there's an approved review associated.
  4. Click Publish.
  5. If any criterion fails, RuleForge shows exactly what needs adjustment.

Common issues​

"Publishing failed"​

The screen shows which criterion is pending. The most common:

  • validation errors appear after a recent edit;
  • a test case broke (regression);
  • the review was never approved;
  • the quality score dropped below the minimum.

Adjust the indicated item and try publishing again.

"I have versions in my plan but don't see all quality criteria"​

Some criteria depend on the contracted plan. See Billing and plans.

Are workspaces the same as versions?​

No. A workspace is a personal draft, useful for iterating without pressure. A version is an official project snapshot, with history, governance, and controlled publishing.