carverauto/serviceradar

Fork 0

chore: release v1.0.60 #2490

Merged

mfreeman451 merged 1 commit from refs/pull/2490/head into main

2025-11-30 18:57:03 +00:00

mfreeman451 commented

2025-11-30 18:56:36 +00:00

(Migrated from github.com)

Owner

Imported from GitHub pull request.

Original GitHub pull request: #2035
Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/pull/2035
Original created: 2025-11-30T18:56:36Z
Original updated: 2025-11-30T18:57:05Z
Original head: carverauto/serviceradar:release/1_0_60
Original base: main
Original merged: 2025-11-30T18:57:03Z 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

Enhancement

Description

Fixed sysmon ingestion to resolve canonical device IDs
Updated UI/device sysmon CPU panels to show mTLS data
Rebuilt and pushed compose-mtls images with new tag
Bumped version from 1.0.59 to 1.0.60

Diagram Walkthrough

flowchart LR
  A["Sysmon Ingestion"] -- "resolve canonical device IDs" --> B["UI/Device Panels"]
  C["Compose-mTLS Images"] -- "rebuild and push" --> D["Stack Refresh"]
  B --> E["v1.0.60 Release"]
  D --> E

File Walkthrough

Relevant files

Documentation

CHANGELOG

Added v1.0.60 release notes and changelog

CHANGELOG

Added v1.0.60 release notes documenting sysmon canonicalization fix
Documented mTLS sysmon-vm checker device ID resolution improvements
Recorded compose-mtls image rebuild with specific SHA tag
Maintained v1.0.59 changelog entry for reference

+10/-0

Configuration changes

VERSION

Bumped version to 1.0.60

VERSION

Updated version number from 1.0.59 to 1.0.60

+1/-1

Imported from GitHub pull request. Original GitHub pull request: #2035 Original author: @mfreeman451 Original URL: https://github.com/carverauto/serviceradar/pull/2035 Original created: 2025-11-30T18:56:36Z Original updated: 2025-11-30T18:57:05Z Original head: carverauto/serviceradar:release/1_0_60 Original base: main Original merged: 2025-11-30T18:57:03Z 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** Enhancement ___ ### **Description** - Fixed sysmon ingestion to resolve canonical device IDs - Updated UI/device sysmon CPU panels to show mTLS data - Rebuilt and pushed compose-mtls images with new tag - Bumped version from 1.0.59 to 1.0.60 ___ ### Diagram Walkthrough ```mermaid flowchart LR A["Sysmon Ingestion"] -- "resolve canonical device IDs" --> B["UI/Device Panels"] C["Compose-mTLS Images"] -- "rebuild and push" --> D["Stack Refresh"] B --> E["v1.0.60 Release"] D --> E ``` <details> <summary><h3> File Walkthrough</h3></summary> <table><thead><tr><th></th><th align="left">Relevant files</th></tr></thead><tbody><tr><td>Documentation</td><td><table> <tr> <td> <details> <summary>CHANGELOG<dd><code>Added v1.0.60 release notes and changelog</code>                                </dd></summary> <hr> CHANGELOG <ul><li>Added v1.0.60 release notes documenting sysmon canonicalization fix <li> Documented mTLS sysmon-vm checker device ID resolution improvements <li> Recorded compose-mtls image rebuild with specific SHA tag <li> Maintained v1.0.59 changelog entry for reference</ul> </details> </td> <td><a href="https://github.com/carverauto/serviceradar/pull/2035/files#diff-ecec88c33adb7591ee6aa88e29b62ad52ef443611cba5e0f0ecac9b5725afdba">+10/-0</a>    </td> </tr> </table></td></tr><tr><td>Configuration changes</td><td><table> <tr> <td> <details> <summary>VERSION<dd><code>Bumped version to 1.0.60</code>                                                                  </dd></summary> <hr> VERSION - Updated version number from 1.0.59 to 1.0.60 </details> </td> <td><a href="https://github.com/carverauto/serviceradar/pull/2035/files#diff-7b60b8e351cbb80c47459ffe2c79f1a26404871f49294780fe47ad0e58c09350">+1/-1</a>      </td> </tr> </table></td></tr></tr></tbody></table> </details> ___

qodo-code-review[bot] commented

2025-11-30 18:56:54 +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/2035#issuecomment-3593107930
Original created: 2025-11-30T18:56:54Z

You are nearing your monthly Qodo Merge usage quota. For more information, please visit here.

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: 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: 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: 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
🔴	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: Sensitive token in docs: The changelog includes a full image tag with a long SHA-like value that may be an internal identifier; consider avoiding publishing sensitive internal tags or confirm they are non-sensitive. Referred Code - Rebuilt/pushed all compose-mtls images with tag `sha-0bc21e5ee79be0eb143cddd6fc7601f739c39f21` and refreshed the stack. Learn more about managing compliance generic rules or creating your own custom rules
⚪	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: No code changes: This PR only updates CHANGELOG and VERSION with no functional code added, so audit trail coverage cannot be assessed from the diff. Referred Code # ServiceRadar v1.0.60 mTLS compose sysmon canonicalization and release rebuild. ## Whats New 1.0.60 - Fixed sysmon ingestion to resolve canonical device IDs so UI/device sysmon CPU panels now show data for mTLS sysmon-vm checkers (e.g., `sr:88239dc2-7208-4c24-a396-3f868c2c9419`). - Rebuilt/pushed all compose-mtls images with tag `sha-0bc21e5ee79be0eb143cddd6fc7601f739c39f21` and refreshed the stack. 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: No code changes: The diff contains no executable code, so error handling cannot be evaluated based on the added lines. Referred Code # ServiceRadar v1.0.60 mTLS compose sysmon canonicalization and release rebuild. ## Whats New 1.0.60 - Fixed sysmon ingestion to resolve canonical device IDs so UI/device sysmon CPU panels now show data for mTLS sysmon-vm checkers (e.g., `sr:88239dc2-7208-4c24-a396-3f868c2c9419`). - Rebuilt/pushed all compose-mtls images with tag `sha-0bc21e5ee79be0eb143cddd6fc7601f739c39f21` and refreshed the stack. 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/2035#issuecomment-3593107930 Original created: 2025-11-30T18:56:54Z --- _You are nearing your monthly Qodo Merge usage quota. For more information, please visit [here](https://qodo-merge-docs.qodo.ai/installation/qodo_merge/#cloud-users)._ ## PR Compliance Guide 🔍  Below is a summary of compliance checks for this PR: <table><tbody><tr><td colspan='2'>Security Compliance</td></tr> <tr><td>🟢</td><td><details><summary>No security concerns identified</summary> No security vulnerabilities detected by AI analysis. Human verification advised for critical code. </details></td></tr> <tr><td colspan='2'>Ticket Compliance</td></tr> <tr><td>⚪</td><td><details><summary>🎫 No ticket provided </summary> - [ ] Create ticket/issue  </details></td></tr> <tr><td colspan='2'>Codebase Duplication Compliance</td></tr> <tr><td>⚪</td><td><details><summary>Codebase context is not defined </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'>Custom Compliance</td></tr> <tr><td rowspan=3>🟢</td><td> <details><summary>Generic: Meaningful Naming and Self-Documenting Code</summary> **Objective:** Ensure all identifiers clearly express their purpose and intent, making code self-documenting **Status:** Passed > 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>Generic: Secure Error Handling</summary> **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 <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>Generic: Security-First Input Validation and Data Handling</summary> **Objective:** Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities **Status:** Passed > 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 rowspan=1>🔴</td> <td><details> <summary>Generic: Secure Logging Practices</summary> **Objective:** To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. **Status:** <a href='https://github.com/carverauto/serviceradar/pull/2035/files#diff-ecec88c33adb7591ee6aa88e29b62ad52ef443611cba5e0f0ecac9b5725afdbaR9-R9'>Sensitive token in docs</a>: The changelog includes a full image tag with a long SHA-like value that may be an internal identifier; consider avoiding publishing sensitive internal tags or confirm they are non-sensitive. <details open><summary>Referred Code</summary> ```txt - Rebuilt/pushed all compose-mtls images with tag `sha-0bc21e5ee79be0eb143cddd6fc7601f739c39f21` and refreshed the stack. ``` </details> > 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 rowspan=2>⚪</td> <td><details> <summary>Generic: Comprehensive Audit Trails</summary> **Objective:** To create a detailed and reliable record of critical system actions for security analysis and compliance. **Status:** <a href='https://github.com/carverauto/serviceradar/pull/2035/files#diff-ecec88c33adb7591ee6aa88e29b62ad52ef443611cba5e0f0ecac9b5725afdbaR1-R10'>No code changes</a>: This PR only updates CHANGELOG and VERSION with no functional code added, so audit trail coverage cannot be assessed from the diff. <details open><summary>Referred Code</summary> ```txt # ServiceRadar v1.0.60 mTLS compose sysmon canonicalization and release rebuild. ## Whats New **1.0.60** - Fixed sysmon ingestion to resolve canonical device IDs so UI/device sysmon CPU panels now show data for mTLS sysmon-vm checkers (e.g., `sr:88239dc2-7208-4c24-a396-3f868c2c9419`). - Rebuilt/pushed all compose-mtls images with tag `sha-0bc21e5ee79be0eb143cddd6fc7601f739c39f21` and refreshed the stack. ``` </details> > 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>Generic: Robust Error Handling and Edge Case Management</summary> **Objective:** Ensure comprehensive error handling that provides meaningful context and graceful degradation **Status:** <a href='https://github.com/carverauto/serviceradar/pull/2035/files#diff-ecec88c33adb7591ee6aa88e29b62ad52ef443611cba5e0f0ecac9b5725afdbaR1-R10'>No code changes</a>: The diff contains no executable code, so error handling cannot be evaluated based on the added lines. <details open><summary>Referred Code</summary> ```txt # ServiceRadar v1.0.60 mTLS compose sysmon canonicalization and release rebuild. ## Whats New **1.0.60** - Fixed sysmon ingestion to resolve canonical device IDs so UI/device sysmon CPU panels now show data for mTLS sysmon-vm checkers (e.g., `sr:88239dc2-7208-4c24-a396-3f868c2c9419`). - Rebuilt/pushed all compose-mtls images with tag `sha-0bc21e5ee79be0eb143cddd6fc7601f739c39f21` and refreshed the stack. ``` </details> > 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 🟡 - Partial Compliant 🔴 - Not Compliant ⚪ - Requires Further Human Verification 🏷️ - Compliance label </details>

qodo-code-review[bot] commented

2025-11-30 18:57:05 +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/2035#issuecomment-3593108351
Original created: 2025-11-30T18:57:05Z

You are nearing your monthly Qodo Merge usage quota. For more information, please visit here.

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/2035#issuecomment-3593108351 Original created: 2025-11-30T18:57:05Z --- _You are nearing your monthly Qodo Merge usage quota. For more information, please visit [here](https://qodo-merge-docs.qodo.ai/installation/qodo_merge/#cloud-users)._ ## PR Code Suggestions ✨ No code suggestions found for the PR.