Files
prowler/api/changelog.d
Daniel Barranquero 8097b8e012 feat(api): track Jira issues per finding and skip already-ticketed findings
New RLS table jira_issues keyed on (integration, provider, finding uid) that
stores the Jira issue key, URL and last observed status for every finding
sent to Jira. send_findings_to_jira() pre-checks the batch in bounded
chunks, refreshes the status of linked issues in bulk, skips findings whose
issue is still open (reported as skipped_count / skipped), creates a
replacement issue when the linked one is closed or deleted in Jira, and
reserves the slot before calling Jira so concurrent runs cannot duplicate.
Read-only GET /api/v1/jira-issues exposes the links with provider-scoped
visibility. Rows are removed with the provider.
2026-08-25 16:58:40 +02:00
..

Changelog fragments

Each PR adds one small file here instead of editing CHANGELOG.md directly, so concurrent PRs never conflict.

  • Filename: <slug>.<type>.md, e.g. my-new-check.added.md (slug is free-form: letters, digits, ., _, -)
  • <type> is one of: added, changed, deprecated, removed, fixed, security
  • Content: one line with the changelog entry text, without the PR link and without a trailing period (the PR link is attached automatically at release time)
  • A PR adds as many fragment files as entries it needs, freely mixing types (one file per entry); same-type entries just use different slugs

Fragments are compiled into CHANGELOG.md when a release is prepared. Full conventions: skills/prowler-changelog/SKILL.md.