fix(jira-integration): Harden Jira URL matching in “Closes …” lists

[marek-saji]

Why?

The jira-integration action’s “Closes …” URL matching had three gaps: Markdown autolink form (<URL>) was not matched, case-variant Jira URLs crashed the action on null.map(), and unescaped dots in the configured Jira origin acted as regexp wildcards, letting look-alike hosts match.

What?

• Match angle-bracket-wrapped (<URL>) Jira URLs in “Closes …” lists, for every item including the first; issue keys are still extracted only via the strict key pattern.
• Use the i flag in the per-match URL extraction as well, so case-variant hosts or issue keys no longer make it return null and crash.
• Escape the configured Jira origin with RegExp.escape() (built in since Node 24, which this action already runs on) before embedding it in the URL regexp.

---

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Reviewed-by: Claude Fable 5 <noreply@anthropic.com>
Reviewed-by: CodeRabbit 0.6.5 <noreply@coderabbit.ai>
Reviewed-by: CodeRabbit <136622811+coderabbitai[bot]@users.noreply.github.com>
Reviewed-by: Codex gpt-5.5 <codex@openai.com>
Reviewed-by: Gemini gemini-2.5-pro <gemini-code-assist@google.com>

[marek-saji]

@coderabbitai review

[coderabbitai]

✅ Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: dfa2f30a-dde9-437c-9c5b-16e1682b3caa

📥 Commits

Reviewing files that changed from the base of the PR and between 5dd12e0 and e4ff700.

📒 Files selected for processing (2)

• .nvmrc
• jira-integration/.nvmrc

💤 Files with no reviewable changes (1)

• jira-integration/.nvmrc

---

📝 Walkthrough

Summary by CodeRabbit

• Bug Fixes
  • Improved detection of Jira issue references in “closes” messages.
  • More reliably matches Jira URLs and extracted issue keys across varying letter casing.
• Chores
  • Updated the project’s Node.js version to v24.18.0.

Walkthrough

The root Node.js version is pinned to v24.18.0, the integration-specific version pin is removed, and Jira resolved-issue extraction now escapes the Jira origin, adjusts “closes” matching, and handles URL matches case-insensitively.

Changes

Jira extraction and runtime

Layer / File(s)	Summary
URL matching and key extraction jira-integration/index.mjs	extractResolvedIssueKeys uses escaped Jira URL origins, an updated “closes” pattern, and case-insensitive URL and issue-key matching.
Node.js runtime version .nvmrc, jira-integration/.nvmrc	The root Node.js version is set to v24.18.0, and the integration-specific version pin is removed.

Estimated code review effort: 2 (Simple) | ~10 minutes

Poem

A rabbit checks the Jira trail,
With safer regex ears held well.
URLs hop through brackets bright,
Keys emerge in matching light.
“Closes!” sings the bunny—done!

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly describes the Jira URL matching hardening and matches the main change in the PR.
Description check	✅ Passed	The description is directly related to the changes and explains the Jira matching fixes.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/jira-integration-url-matching

---

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