LinearB On-Prem Agent v4.2.6

Released 2026-06-18.

A maintenance release. The main fix restores custom root CA trust inside the pods that run analysis jobs; the rest is a batch of accuracy and reliability improvements to the Jira, GitHub and gitStream integrations.

Bug fixes

• Custom root certificates are trusted again inside job pods. Since v4.2.3, the certificate bundle was merged into the long-running services but not into the pods the agent creates to run code, project-management and sensor jobs, so those jobs could not reach a self-hosted SCM or project-management tool behind a private CA. Only installations with CUSTOM_ROOT_CERTIFICATES enabled were affected; nothing changes when custom certificates are not configured
• Jira: raw collected files are published under the correct prefix again when several organizations are collected in the same run, and the agent now reports when a run finished with no files to upload rather than completing silently
• Jira: a selective custom-field list written with spaces between entries is accepted instead of being rejected as malformed
• gitStream keeps an AI-review approval in place when an unrelated recalculation runs, and only dismisses its own approval when an approve automation actually ran for that change
• gitStream no longer reprocesses the same event after a long-running rule evaluation, which was caused by an internal queue timing out before its consumer finished
• Amazon Q and Kiro integrations: the access check now recognises Kiro as a provider instead of reporting the integration as unreachable

Improvements

• The GitHub Issues collector gathers the full set of issue fields
• Pull requests opened by a bot and later taken over by a person are attributed to the person
• GitLab: a commit status is now always resolved for a pull request, even when the first attempt to post it fails
• The post-deployment integrations guide has been corrected and simplified: the add-git-integration example could not be copy-pasted, the steps were misnumbered, and placeholders such as <integration_id> were written inconsistently

Component versions