Add signature header support to Exolix

[peachbits]

CHANGELOG

Does this branch warrant an entry to the CHANGELOG?

• Yes
• No

Dependencies

none

Description

none

---

Note

Medium Risk
Partner sync stops until both apiKey and signature are configured; misconfiguration can silently yield empty Exolix transaction pulls.

Overview
Exolix partner reporting now requires a signature credential alongside apiKey, and sends it on every Exolix API v2 transaction list request.

Plugin params validation accepts an optional signature in apiKeys. queryExolix returns no transactions (same as a missing API key) when either credential is absent, and adds a signature HTTP header next to Authorization. The unreleased changelog notes the change.

^{Reviewed by Cursor Bugbot for commit 7206b94. Bugbot is set up for automated code reviews on this repo. Configure here.}

---

• To see the specific tasks where the Asana app for GitHub is being used, see below:
  • https://app.asana.com/0/0/1215305713887495