shashank-elastic

We can use `python -m detection_rules dev test-version-lock main` to test this logic change

**Testing Updates During Release part** - We patched the code to 8.18 and 9.0 branches locally and tested lock versions - We ran this command on 8.18 and 9.0 `python...

Checked with @Samirbous Can be skipped for this release cycle.

**Am running the test here** with GITHUB_TOKEN --> https://github.com/elastic/detection-rules/actions/runs/15141279107 with WRITE_KIBANA_DETECTION_RULES_TOKEN --> https://github.com/elastic/detection-rules/actions/runs/15141096361 Both the token seems to not have access to comment on issues is what i am understanding...

> I think this has to do with the change in this PR to the `uses: peter-evans/create-or-update-comment@v4` as writing/creating issues vs comments is the same authentication level (both of which...

> Yes, the curl I sent was from the original workflow to illustrate how this PR shifts the existing approach; going from a low dependency method, to a high dependency...

**23 Oct 2025** With ESQL Remote Validation merged https://github.com/elastic/detection-rules/pull/4955, this can now be used to populate related_integrations and required_fields for ESQL rules. Release Fleet [workflow](https://github.com/elastic/detection-rules/blob/main/.github/workflows/release-fleet.yml ) would have the below...

These are min_stack version updates :slightly_smiling_face: Part of the PR https://github.com/elastic/detection-rules/pull/4273 With the changing requirements of the integration versions, we identify the kibana version to minstack for rules. Where no...

### Notable Debugging and Root Cause Identification - For the Rules listed above we have seen a major identifier that the related integration filed is not populated. - For example...

**Spot Check on My Test Stack** - Works as Expected Rules --> Meaning the Version Diff shows related integration Field, Kibana Asset has the related integration filed populated | Rule...