ci: ignore helm scope in git-cliff

[M0NsTeRRR]

Description

Ignore helm scope in git-cliff so we can use whatever conventional commit "type".
Refactored a bit the config to drop unused config.

How Has This Been Tested?

Screenshots / Logs (if applicable)

Checklist:

• I have read and followed the contribution guidelines.
• Disclosed any use of AI (see our policy)
• I have updated the documentation accordingly.
• All new and existing tests passed.
• Successful build pnpm build
• Translation keys pnpm i18n:extract
• Database migration (if required)

Summary by CodeRabbit

• Chores
  • Updated release-note generation rules: now skips Helm and certain automated chore/dependency-release commits, elevates security entries to the top group, reorders feature/fix groups for clearer presentation, reclassifies legacy groups (refactor, style, test, chore/CI, revert) into new indices, and removed explicit CI-skip patterns to simplify commit classification.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 533a7a65-f683-4a03-84e4-9b30846b4f6a

📥 Commits

Reviewing files that changed from the base of the PR and between 18468c4 and 84a3b8c.

📒 Files selected for processing (1)

• .github/cliff.toml

🚧 Files skipped from review as they are similar to previous changes (1)

• .github/cliff.toml

---

📝 Walkthrough

Walkthrough

Updated .github/cliff.toml commit_parsers: added helm and chore skip rules, introduced a security group, reordered and relabeled several commit groups (feat, fix, doc, perf, refactor, style, test, chore/ci, revert), and removed two skip-ci preprocessor patterns.

Changes

Cohort / File(s)	Summary
Changelog configuration .github/cliff.toml	Added commit_parsers entries for helm and chore skips and a security body matcher; reordered and relabeled groups for feat, fix, doc, perf, refactor, style, test, `chore

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Suggested reviewers

• fallenbagel
• sudo-kraken
• 0xSysR3ll

Poem

🐰 I hopped through toml lines, tidy and neat,
Placed security forward and skipped a few beats.
I nudged feats and fixes into ordered array,
Nibbled old CI skips and hopped away. ✨

🚥 Pre-merge checks | ✅ 2

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title "ci: ignore helm scope in git-cliff" accurately describes the primary change: updating git-cliff configuration to ignore the helm scope, allowing conventional commits to work regardless of that scope.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In @.github/cliff.toml:
- Line 89: The skip rule "{ message = '.*\\(helm\\).*', skip = true }" is placed
after the grouping commit_parsers so it never matches; move this helm skip rule
to appear before the grouping rules in the commit_parsers array so it gets
evaluated first (ensuring commits like "feat(helm): ..." are skipped) and keep
the rest of the grouping rules (the ^feat, ^fix, etc.) following it.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: f3fe68ae-fc03-4df0-aa30-858262929e22

📥 Commits

Reviewing files that changed from the base of the PR and between 1548948 and 582d08a.

📒 Files selected for processing (1)

• .github/cliff.toml

[coderabbitai]

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In @.github/cliff.toml:
- Around line 73-74: The TOML strings for the regex entries { message =
"^chore\(release\): prepare for", skip = true } and { message =
"^chore\(deps.*\)", skip = true } use invalid escape sequences (\( and \))
inside double-quoted strings; change each to either single-quoted literal
strings (e.g. message = '^chore\(release\): prepare for') or double-escape the
backslashes in the existing double quotes (e.g. message = "^chore\\(release\\):
prepare for") so the TOML parser accepts the regexes.
- Around line 75-77: The security parser { body = ".*security", group = "<!-- 0
-->🛡️ Security" } is listed before the type-specific parsers and will match
first, overriding commits that should be grouped by message patterns like {
message = "^feat", group = "<!-- 1 -->🚀 Features" } and { message = "^fix",
group = "<!-- 2 -->🐛 Bug Fixes" }; reorder the entries so the message-based
parsers (the "^feat" and "^fix" rules) appear before the body-based security
rule to ensure type-specific grouping wins, leaving the security rule lower in
the list to only catch leftover commits mentioning "security".

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: e08248dd-cc05-4ca0-9c99-dfe1563b2708

📥 Commits

Reviewing files that changed from the base of the PR and between 83f8bb2 and 18468c4.

📒 Files selected for processing (1)

• .github/cliff.toml