carverauto/serviceradar

Fork 0

chore: release v1.0.91 #2850

Merged

mfreeman451 merged 1 commit from refs/pull/2850/head into staging

2026-02-04 22:56:20 +00:00

mfreeman451 commented

2026-02-04 22:56:01 +00:00

(Migrated from github.com)

Owner

Imported from GitHub pull request.

Original GitHub pull request: #2699
Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/pull/2699
Original created: 2026-02-04T22:56:01Z
Original updated: 2026-02-04T22:56:41Z
Original head: carverauto/serviceradar:releases/1_0_91
Original base: staging
Original merged: 2026-02-04T22:56:20Z by @mfreeman451

User description

IMPORTANT: Please sign the Developer Certificate of Origin

Thank you for your contribution to ServiceRadar. Please note, when contributing, the developer must include
a DCO sign-off statement indicating the DCO acceptance in one commit message. Here
is an example DCO Signed-off-by line in a commit message:

Signed-off-by: J. Doe <j.doe@domain.com>

Describe your changes

Issue ticket number and link

Code checklist before requesting a review

I have signed the DCO?
The build completes without errors?
All tests are passing when running make test?

PR Type

Other

Description

Release version 1.0.91 with Docker compose stability fixes
Agent gateway resolution and core-elx build improvements
Database migration and sequence ownership fixes

Diagram Walkthrough

flowchart LR
  A["Version Update<br/>1.0.90 → 1.0.91"] --> B["CHANGELOG<br/>Release Notes"]
  A --> C["Helm Chart<br/>Version Bump"]
  B --> D["Agent Gateway<br/>Enrollment Fix"]
  B --> E["Core-elx Build<br/>Rust Toolchain"]
  B --> F["Database Migrations<br/>Search Path"]

File Walkthrough

Relevant files

Documentation

CHANGELOG

Add v1.0.91 release notes and fixes

CHANGELOG

Added release notes for v1.0.91 at the top of the file
Documented Docker compose agent gateway resolution fix via
agent-gateway.serviceradar
Documented core-elx Docker build improvements for Rust workspace and
SRQL NIF compilation
Documented startup migration fixes for database search_path and AGE
sequence ownership

+11/-0

Configuration changes

VERSION `Bump version to 1.0.91` VERSION Updated version number from 1.0.90 to 1.0.91	+1/-1
Chart.yaml `Update Helm chart to v1.0.91` helm/serviceradar/Chart.yaml Updated Helm chart version from 1.0.90 to 1.0.91 Updated appVersion from 1.0.90 to 1.0.91	+2/-2

Imported from GitHub pull request. Original GitHub pull request: #2699 Original author: @mfreeman451 Original URL: https://github.com/carverauto/serviceradar/pull/2699 Original created: 2026-02-04T22:56:01Z Original updated: 2026-02-04T22:56:41Z Original head: carverauto/serviceradar:releases/1_0_91 Original base: staging Original merged: 2026-02-04T22:56:20Z by @mfreeman451 --- ### **User description** ## IMPORTANT: Please sign the Developer Certificate of Origin Thank you for your contribution to ServiceRadar. Please note, when contributing, the developer must include a [DCO sign-off statement]( https://developercertificate.org/) indicating the DCO acceptance in one commit message. Here is an example DCO Signed-off-by line in a commit message: ``` Signed-off-by: J. Doe <j.doe@domain.com> ``` ## Describe your changes ## Issue ticket number and link ## Code checklist before requesting a review - [ ] I have signed the DCO? - [ ] The build completes without errors? - [ ] All tests are passing when running make test? ___ ### **PR Type** Other ___ ### **Description** - Release version 1.0.91 with Docker compose stability fixes - Agent gateway resolution and core-elx build improvements - Database migration and sequence ownership fixes ___ ### Diagram Walkthrough ```mermaid flowchart LR A["Version Update<br/>1.0.90 → 1.0.91"] --> B["CHANGELOG<br/>Release Notes"] A --> C["Helm Chart<br/>Version Bump"] B --> D["Agent Gateway<br/>Enrollment Fix"] B --> E["Core-elx Build<br/>Rust Toolchain"] B --> F["Database Migrations<br/>Search Path"] ``` <details><summary><h3>File Walkthrough</h3></summary> <table><thead><tr><th></th><th align="left">Relevant files</th></tr></thead><tbody><tr><td><strong>Documentation</strong></td><td><table> <tr> <td> <details> <summary><strong>CHANGELOG</strong><dd><code>Add v1.0.91 release notes and fixes</code>                                            </dd></summary> <hr> CHANGELOG <ul><li>Added release notes for v1.0.91 at the top of the file<br> <li> Documented Docker compose agent gateway resolution fix via <br><code>agent-gateway.serviceradar</code><br> <li> Documented core-elx Docker build improvements for Rust workspace and <br>SRQL NIF compilation<br> <li> Documented startup migration fixes for database search_path and AGE <br>sequence ownership</ul> </details> </td> <td><a href="https://github.com/carverauto/serviceradar/pull/2699/files#diff-ecec88c33adb7591ee6aa88e29b62ad52ef443611cba5e0f0ecac9b5725afdba">+11/-0</a>    </td> </tr> </table></td></tr><tr><td><strong>Configuration changes</strong></td><td><table> <tr> <td> <details> <summary><strong>VERSION</strong><dd><code>Bump version to 1.0.91</code>                                                                      </dd></summary> <hr> VERSION - Updated version number from 1.0.90 to 1.0.91 </details> </td> <td><a href="https://github.com/carverauto/serviceradar/pull/2699/files#diff-7b60b8e351cbb80c47459ffe2c79f1a26404871f49294780fe47ad0e58c09350">+1/-1</a>      </td> </tr> <tr> <td> <details> <summary><strong>Chart.yaml</strong><dd><code>Update Helm chart to v1.0.91</code>                                                          </dd></summary> <hr> helm/serviceradar/Chart.yaml <ul><li>Updated Helm chart version from 1.0.90 to 1.0.91<br> <li> Updated appVersion from 1.0.90 to 1.0.91</ul> </details> </td> <td><a href="https://github.com/carverauto/serviceradar/pull/2699/files#diff-5da50230d0b5d4b5e859c40708517b85481711881faaf741e74cd58aa99314f8">+2/-2</a>      </td> </tr> </table></td></tr></tbody></table> </details> ___

qodo-code-review[bot] commented

2026-02-04 22:56:22 +00:00

(Migrated from github.com)

Author

Owner

Imported GitHub PR comment.

Original author: @qodo-code-review[bot]
Original URL: https://github.com/carverauto/serviceradar/pull/2699#issuecomment-3850151484
Original created: 2026-02-04T22:56:22Z

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢	No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
🟢	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: Passed Learn more about managing compliance generic rules or creating your own custom rules

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

Imported GitHub PR comment. Original author: @qodo-code-review[bot] Original URL: https://github.com/carverauto/serviceradar/pull/2699#issuecomment-3850151484 Original created: 2026-02-04T22:56:22Z --- ## PR Compliance Guide 🔍  Below is a summary of compliance checks for this PR:<br> <table><tbody><tr><td colspan='2'><strong>Security Compliance</strong></td></tr> <tr><td>🟢</td><td><details><summary><strong>No security concerns identified</strong></summary> No security vulnerabilities detected by AI analysis. Human verification advised for critical code. </details></td></tr> <tr><td colspan='2'><strong>Ticket Compliance</strong></td></tr> <tr><td>⚪</td><td><details><summary>🎫 <strong>No ticket provided </strong></summary> - [ ] Create ticket/issue  </details></td></tr> <tr><td colspan='2'><strong>Codebase Duplication Compliance</strong></td></tr> <tr><td>⚪</td><td><details><summary><strong>Codebase context is not defined </strong></summary> Follow the <a href='https://qodo-merge-docs.qodo.ai/core-abilities/rag_context_enrichment/'>guide</a> to enable codebase context checks. </details></td></tr> <tr><td colspan='2'><strong>Custom Compliance</strong></td></tr> <tr><td rowspan=6>🟢</td><td> <details><summary><strong>Generic: Comprehensive Audit Trails</strong></summary><br> **Objective:** To create a detailed and reliable record of critical system actions for security analysis <br>and compliance.<br> **Status:** Passed<br> > Learn more about managing compliance <a href='https://qodo-merge-docs.qodo.ai/tools/compliance/#configuration-options'>generic rules</a> or creating your own <a href='https://qodo-merge-docs.qodo.ai/tools/compliance/#custom-compliance'>custom rules</a> </details></td></tr> <tr><td> <details><summary><strong>Generic: Meaningful Naming and Self-Documenting Code</strong></summary><br> **Objective:** Ensure all identifiers clearly express their purpose and intent, making code <br>self-documenting<br> **Status:** Passed<br> > Learn more about managing compliance <a href='https://qodo-merge-docs.qodo.ai/tools/compliance/#configuration-options'>generic rules</a> or creating your own <a href='https://qodo-merge-docs.qodo.ai/tools/compliance/#custom-compliance'>custom rules</a> </details></td></tr> <tr><td> <details><summary><strong>Generic: Robust Error Handling and Edge Case Management</strong></summary><br> **Objective:** Ensure comprehensive error handling that provides meaningful context and graceful <br>degradation<br> **Status:** Passed<br> > Learn more about managing compliance <a href='https://qodo-merge-docs.qodo.ai/tools/compliance/#configuration-options'>generic rules</a> or creating your own <a href='https://qodo-merge-docs.qodo.ai/tools/compliance/#custom-compliance'>custom rules</a> </details></td></tr> <tr><td> <details><summary><strong>Generic: Secure Error Handling</strong></summary><br> **Objective:** To prevent the leakage of sensitive system information through error messages while <br>providing sufficient detail for internal debugging.<br> **Status:** Passed<br> > Learn more about managing compliance <a href='https://qodo-merge-docs.qodo.ai/tools/compliance/#configuration-options'>generic rules</a> or creating your own <a href='https://qodo-merge-docs.qodo.ai/tools/compliance/#custom-compliance'>custom rules</a> </details></td></tr> <tr><td> <details><summary><strong>Generic: Secure Logging Practices</strong></summary><br> **Objective:** To ensure logs are useful for debugging and auditing without exposing sensitive <br>information like PII, PHI, or cardholder data.<br> **Status:** Passed<br> > Learn more about managing compliance <a href='https://qodo-merge-docs.qodo.ai/tools/compliance/#configuration-options'>generic rules</a> or creating your own <a href='https://qodo-merge-docs.qodo.ai/tools/compliance/#custom-compliance'>custom rules</a> </details></td></tr> <tr><td> <details><summary><strong>Generic: Security-First Input Validation and Data Handling</strong></summary><br> **Objective:** Ensure all data inputs are validated, sanitized, and handled securely to prevent <br>vulnerabilities<br> **Status:** Passed<br> > Learn more about managing compliance <a href='https://qodo-merge-docs.qodo.ai/tools/compliance/#configuration-options'>generic rules</a> or creating your own <a href='https://qodo-merge-docs.qodo.ai/tools/compliance/#custom-compliance'>custom rules</a> </details></td></tr> <tr><td align="center" colspan="2">   </td></tr></tbody></table> <details><summary>Compliance status legend</summary> 🟢 - Fully Compliant<br> 🟡 - Partial Compliant<br> 🔴 - Not Compliant<br> ⚪ - Requires Further Human Verification<br> 🏷️ - Compliance label<br> </details>

qodo-code-review[bot] commented

2026-02-04 22:56:41 +00:00

(Migrated from github.com)

Author

Owner

Imported GitHub PR comment.

Original author: @qodo-code-review[bot]
Original URL: https://github.com/carverauto/serviceradar/pull/2699#issuecomment-3850152384
Original created: 2026-02-04T22:56:41Z

PR Code Suggestions ✨

No code suggestions found for the PR.

Imported GitHub PR comment. Original author: @qodo-code-review[bot] Original URL: https://github.com/carverauto/serviceradar/pull/2699#issuecomment-3850152384 Original created: 2026-02-04T22:56:41Z --- ## PR Code Suggestions ✨ No code suggestions found for the PR.