LinearB On-Prem Agent v5.0.1

Released 2026-08-12.

A maintenance release: long-running jobs get more time to finish, gitStream and the project-management connectors pick up a batch of accuracy and reliability fixes, and the bundled Redis, RabbitMQ and NGINX images move to current patched versions.

Action required

• Plan for in-flight jobs when you upgrade. This release replaces the Redis pod, and Redis runs without persistence, so the job-state database is cleared. Jobs that are still running at that moment are treated as orphaned and removed — they are not retried and no completion is reported. Let running job suites drain first, or upgrade during a quiet window.

Bug fixes

• Bitbucket pull requests no longer go unprocessed when the trigger payload is too large. Payloads are now compressed, and anything still over the limit is passed by reference, which removes by far the most common cause of skipped Bitbucket automations
• Bitbucket Server: pull requests merged or updated outside the agent are now picked up, and merge and update timestamps are read correctly
• gitStream re-approves a pull request when a new commit dismissed an earlier approval
• gitStream shows the underlying message instead of undefined when an AI-generated description comes back empty
• Amazon Q and Kiro metrics are collected correctly on AWS Organizations setups that span multiple accounts, where they previously came back empty
• Jira change history imported in bulk now records timestamps in the correct format, and a sprint being assigned for the first time or removed entirely no longer fails the import
• Branch-to-issue matching is more reliable when several project-management integrations are connected, including when two of them claim the same branch
• Branches stuck waiting on commits that never arrived can now recover on their own instead of staying stuck
• Story points explicitly set to zero are now reported as zero rather than as no value at all
• AWS load balancer annotations for the webhook receiver are applied correctly when the agent is installed under a custom Helm release name

Improvements

• Long-running jobs now get up to four hours to finish instead of one. This applies to every job the agent runs — code, project-management, sensors and operational jobs
• A new pr.author_type value is available in gitStream rules, so automations can distinguish human authors from bots across GitHub, GitLab and Bitbucket
• New guide for running the agent behind a corporate HTTP proxy
• Quieter logs: expected "not found" responses from Jira and deleted source branches in the gitStream playground are no longer recorded as errors
• Cursor integrations now request the admin:read scope

Security and dependency updates

• Redis updated to 8.2.8
• RabbitMQ moved to a hardened base image with a reduced vulnerability surface
• Forward-proxy NGINX updated from 1.29.8 to 1.30.4
• npm updated in the gitStream image to resolve CVE-2026-59873
• Sensor authorization tokens are no longer carried in job payloads; they are fetched at the point of use instead
• The legacy Jira OAuth1 key endpoint, which returned a shared secret to any caller, has been removed

Known issues, fixed in v5.0.2

• Running behind a corporate proxy in transparent mode does not work in this release: the agent presents an internal cluster name during the TLS handshake rather than the real API hostname. connect mode works where the proxy tolerates the mismatch. Fixed in v5.0.2, with no configuration change needed
• The corporate-proxy guide published with this release configures Datadog through a values key that Helm replaces rather than merges, which silently removes the RabbitMQ credentials the Datadog agent needs. If you followed that guide, see the v5.0.2 notes for what to change

Component versions