carverauto/serviceradar

Fork 0

chore: release v1.0.68 #2544

Merged

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

2025-12-11 06:51:01 +00:00

mfreeman451 commented

2025-12-11 06:45:29 +00:00

(Migrated from github.com)

Owner

Imported from GitHub pull request.

Original GitHub pull request: #2105
Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/pull/2105
Original created: 2025-12-11T06:45:29Z
Original updated: 2025-12-11T06:51:04Z
Original head: carverauto/serviceradar:release/1_0_68
Original base: main
Original merged: 2025-12-11T06:51:01Z 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.68 with Docker Compose improvements
Restored KV-backed configuration seeding in Docker Compose
Hardened db-event-writer JetStream consumer with retry logic
Added NATS context to serviceradar-tools for local inspection
Zen ignores initial KV watch event to prevent spurious restarts

Diagram Walkthrough

flowchart LR
  A["Version 1.0.67"] -- "Release" --> B["Version 1.0.68"]
  B --> C["KV Configuration Seeding"]
  B --> D["JetStream Consumer Hardening"]
  B --> E["NATS Context Bundling"]
  B --> F["Zen KV Watch Fix"]

File Walkthrough

Relevant files

Documentation

CHANGELOG

Added v1.0.68 release notes and features

CHANGELOG

Added v1.0.68 release notes at the top of the file
Documented KV-backed configuration seeding restoration in Docker
Compose
Listed JetStream consumer hardening improvements
Noted NATS context bundling in serviceradar-tools
Documented Zen KV watch event filtering behavior

+12/-0

Configuration changes

VERSION

Bumped version to 1.0.68

VERSION

Updated version number from 1.0.67 to 1.0.68

+1/-1

Imported from GitHub pull request. Original GitHub pull request: #2105 Original author: @mfreeman451 Original URL: https://github.com/carverauto/serviceradar/pull/2105 Original created: 2025-12-11T06:45:29Z Original updated: 2025-12-11T06:51:04Z Original head: carverauto/serviceradar:release/1_0_68 Original base: main Original merged: 2025-12-11T06:51:01Z 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.68 with Docker Compose improvements - Restored KV-backed configuration seeding in Docker Compose - Hardened db-event-writer JetStream consumer with retry logic - Added NATS context to serviceradar-tools for local inspection - Zen ignores initial KV watch event to prevent spurious restarts ___ ### Diagram Walkthrough ```mermaid flowchart LR A["Version 1.0.67"] -- "Release" --> B["Version 1.0.68"] B --> C["KV Configuration Seeding"] B --> D["JetStream Consumer Hardening"] B --> E["NATS Context Bundling"] B --> F["Zen KV Watch Fix"] ``` <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.68 release notes and features</code>                                  </dd></summary> <hr> CHANGELOG <ul><li>Added v1.0.68 release notes at the top of the file <li> Documented KV-backed configuration seeding restoration in Docker Compose <li> Listed JetStream consumer hardening improvements <li> Noted NATS context bundling in serviceradar-tools <li> Documented Zen KV watch event filtering behavior</ul> </details> </td> <td><a href="https://github.com/carverauto/serviceradar/pull/2105/files#diff-ecec88c33adb7591ee6aa88e29b62ad52ef443611cba5e0f0ecac9b5725afdba">+12/-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.68</code>                                                                  </dd></summary> <hr> VERSION - Updated version number from 1.0.67 to 1.0.68 </details> </td> <td><a href="https://github.com/carverauto/serviceradar/pull/2105/files#diff-7b60b8e351cbb80c47459ffe2c79f1a26404871f49294780fe47ad0e58c09350">+1/-1</a>      </td> </tr> </table></td></tr></tbody></table> </details> ___

qodo-code-review[bot] commented

2025-12-11 06:45:52 +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/2105#issuecomment-3640483386
Original created: 2025-12-11T06:45:52Z

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: No code changes: The PR adds only documentation and version updates without executable code, so audit trail compliance cannot be assessed from the diff. Referred Code # ServiceRadar v1.0.68 Docker Compose KV seeding restored and JetStream consumers hardened. ## Whats New 1.0.68 - Restored KV-backed configuration seeding in Docker Compose (including poller stack) so core/agent/poller/zen/db-event-writer bootstrap datasvc and surface in the UI; docs updated accordingly. - Bundled a Compose-ready NATS context inside `serviceradar-tools` for local JetStream/KV inspection without pulling extra images. - Hardened the db-event-writer JetStream consumer with retrying connection/setup logic to survive NATS restarts during Compose bring-up. - Zen now ignores the initial KV watch event when CONFIG_SOURCE=kv to avoid spurious restarts on first sync. 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: No identifiers added: Only CHANGELOG text and VERSION were updated; no new code identifiers were introduced to evaluate naming. Referred Code # ServiceRadar v1.0.68 Docker Compose KV seeding restored and JetStream consumers hardened. ## Whats New 1.0.68 - Restored KV-backed configuration seeding in Docker Compose (including poller stack) so core/agent/poller/zen/db-event-writer bootstrap datasvc and surface in the UI; docs updated accordingly. - Bundled a Compose-ready NATS context inside `serviceradar-tools` for local JetStream/KV inspection without pulling extra images. - Hardened the db-event-writer JetStream consumer with retrying connection/setup logic to survive NATS restarts during Compose bring-up. - Zen now ignores the initial KV watch event when CONFIG_SOURCE=kv to avoid spurious restarts on first sync. 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 executable logic: The diff contains no functional code or error handling paths to assess robustness or edge case management. Referred Code # ServiceRadar v1.0.68 Docker Compose KV seeding restored and JetStream consumers hardened. ## Whats New 1.0.68 - Restored KV-backed configuration seeding in Docker Compose (including poller stack) so core/agent/poller/zen/db-event-writer bootstrap datasvc and surface in the UI; docs updated accordingly. - Bundled a Compose-ready NATS context inside `serviceradar-tools` for local JetStream/KV inspection without pulling extra images. - Hardened the db-event-writer JetStream consumer with retrying connection/setup logic to survive NATS restarts during Compose bring-up. - Zen now ignores the initial KV watch event when CONFIG_SOURCE=kv to avoid spurious restarts on first sync. 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: No user errors changed: There are no user-facing error messages or error-handling code in the diff to evaluate for sensitive information leakage. Referred Code # ServiceRadar v1.0.68 Docker Compose KV seeding restored and JetStream consumers hardened. ## Whats New 1.0.68 - Restored KV-backed configuration seeding in Docker Compose (including poller stack) so core/agent/poller/zen/db-event-writer bootstrap datasvc and surface in the UI; docs updated accordingly. - Bundled a Compose-ready NATS context inside `serviceradar-tools` for local JetStream/KV inspection without pulling extra images. - Hardened the db-event-writer JetStream consumer with retrying connection/setup logic to survive NATS restarts during Compose bring-up. - Zen now ignores the initial KV watch event when CONFIG_SOURCE=kv to avoid spurious restarts on first sync. 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: No logging code: No new or modified logging statements are present; secure logging compliance cannot be determined from this diff. Referred Code # ServiceRadar v1.0.68 Docker Compose KV seeding restored and JetStream consumers hardened. ## Whats New 1.0.68 - Restored KV-backed configuration seeding in Docker Compose (including poller stack) so core/agent/poller/zen/db-event-writer bootstrap datasvc and surface in the UI; docs updated accordingly. - Bundled a Compose-ready NATS context inside `serviceradar-tools` for local JetStream/KV inspection without pulling extra images. - Hardened the db-event-writer JetStream consumer with retrying connection/setup logic to survive NATS restarts during Compose bring-up. - Zen now ignores the initial KV watch event when CONFIG_SOURCE=kv to avoid spurious restarts on first sync. 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: No input handling: The PR does not introduce code that handles external inputs; validation and data handling cannot be assessed from the provided changes. Referred Code # ServiceRadar v1.0.68 Docker Compose KV seeding restored and JetStream consumers hardened. ## Whats New 1.0.68 - Restored KV-backed configuration seeding in Docker Compose (including poller stack) so core/agent/poller/zen/db-event-writer bootstrap datasvc and surface in the UI; docs updated accordingly. - Bundled a Compose-ready NATS context inside `serviceradar-tools` for local JetStream/KV inspection without pulling extra images. - Hardened the db-event-writer JetStream consumer with retrying connection/setup logic to survive NATS restarts during Compose bring-up. - Zen now ignores the initial KV watch event when CONFIG_SOURCE=kv to avoid spurious restarts on first sync. 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/2105#issuecomment-3640483386 Original created: 2025-12-11T06:45:52Z --- ## 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=6>⚪</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/2105/files#diff-ecec88c33adb7591ee6aa88e29b62ad52ef443611cba5e0f0ecac9b5725afdbaR1-R12'>No code changes</a>: The PR adds only documentation and version updates without executable code, so audit trail compliance cannot be assessed from the diff. <details open><summary>Referred Code</summary> ```txt # ServiceRadar v1.0.68 Docker Compose KV seeding restored and JetStream consumers hardened. ## Whats New **1.0.68** - Restored KV-backed configuration seeding in Docker Compose (including poller stack) so core/agent/poller/zen/db-event-writer bootstrap datasvc and surface in the UI; docs updated accordingly. - Bundled a Compose-ready NATS context inside `serviceradar-tools` for local JetStream/KV inspection without pulling extra images. - Hardened the db-event-writer JetStream consumer with retrying connection/setup logic to survive NATS restarts during Compose bring-up. - Zen now ignores the initial KV watch event when CONFIG_SOURCE=kv to avoid spurious restarts on first sync. ``` </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: Meaningful Naming and Self-Documenting Code</summary> **Objective:** Ensure all identifiers clearly express their purpose and intent, making code self-documenting **Status:** <a href='https://github.com/carverauto/serviceradar/pull/2105/files#diff-ecec88c33adb7591ee6aa88e29b62ad52ef443611cba5e0f0ecac9b5725afdbaR1-R12'>No identifiers added</a>: Only CHANGELOG text and VERSION were updated; no new code identifiers were introduced to evaluate naming. <details open><summary>Referred Code</summary> ```txt # ServiceRadar v1.0.68 Docker Compose KV seeding restored and JetStream consumers hardened. ## Whats New **1.0.68** - Restored KV-backed configuration seeding in Docker Compose (including poller stack) so core/agent/poller/zen/db-event-writer bootstrap datasvc and surface in the UI; docs updated accordingly. - Bundled a Compose-ready NATS context inside `serviceradar-tools` for local JetStream/KV inspection without pulling extra images. - Hardened the db-event-writer JetStream consumer with retrying connection/setup logic to survive NATS restarts during Compose bring-up. - Zen now ignores the initial KV watch event when CONFIG_SOURCE=kv to avoid spurious restarts on first sync. ``` </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/2105/files#diff-ecec88c33adb7591ee6aa88e29b62ad52ef443611cba5e0f0ecac9b5725afdbaR1-R12'>No executable logic</a>: The diff contains no functional code or error handling paths to assess robustness or edge case management. <details open><summary>Referred Code</summary> ```txt # ServiceRadar v1.0.68 Docker Compose KV seeding restored and JetStream consumers hardened. ## Whats New **1.0.68** - Restored KV-backed configuration seeding in Docker Compose (including poller stack) so core/agent/poller/zen/db-event-writer bootstrap datasvc and surface in the UI; docs updated accordingly. - Bundled a Compose-ready NATS context inside `serviceradar-tools` for local JetStream/KV inspection without pulling extra images. - Hardened the db-event-writer JetStream consumer with retrying connection/setup logic to survive NATS restarts during Compose bring-up. - Zen now ignores the initial KV watch event when CONFIG_SOURCE=kv to avoid spurious restarts on first sync. ``` </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: Secure Error Handling</summary> **Objective:** To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. **Status:** <a href='https://github.com/carverauto/serviceradar/pull/2105/files#diff-ecec88c33adb7591ee6aa88e29b62ad52ef443611cba5e0f0ecac9b5725afdbaR1-R12'>No user errors changed</a>: There are no user-facing error messages or error-handling code in the diff to evaluate for sensitive information leakage. <details open><summary>Referred Code</summary> ```txt # ServiceRadar v1.0.68 Docker Compose KV seeding restored and JetStream consumers hardened. ## Whats New **1.0.68** - Restored KV-backed configuration seeding in Docker Compose (including poller stack) so core/agent/poller/zen/db-event-writer bootstrap datasvc and surface in the UI; docs updated accordingly. - Bundled a Compose-ready NATS context inside `serviceradar-tools` for local JetStream/KV inspection without pulling extra images. - Hardened the db-event-writer JetStream consumer with retrying connection/setup logic to survive NATS restarts during Compose bring-up. - Zen now ignores the initial KV watch event when CONFIG_SOURCE=kv to avoid spurious restarts on first sync. ``` </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: 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/2105/files#diff-ecec88c33adb7591ee6aa88e29b62ad52ef443611cba5e0f0ecac9b5725afdbaR1-R12'>No logging code</a>: No new or modified logging statements are present; secure logging compliance cannot be determined from this diff. <details open><summary>Referred Code</summary> ```txt # ServiceRadar v1.0.68 Docker Compose KV seeding restored and JetStream consumers hardened. ## Whats New **1.0.68** - Restored KV-backed configuration seeding in Docker Compose (including poller stack) so core/agent/poller/zen/db-event-writer bootstrap datasvc and surface in the UI; docs updated accordingly. - Bundled a Compose-ready NATS context inside `serviceradar-tools` for local JetStream/KV inspection without pulling extra images. - Hardened the db-event-writer JetStream consumer with retrying connection/setup logic to survive NATS restarts during Compose bring-up. - Zen now ignores the initial KV watch event when CONFIG_SOURCE=kv to avoid spurious restarts on first sync. ``` </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: Security-First Input Validation and Data Handling</summary> **Objective:** Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities **Status:** <a href='https://github.com/carverauto/serviceradar/pull/2105/files#diff-ecec88c33adb7591ee6aa88e29b62ad52ef443611cba5e0f0ecac9b5725afdbaR1-R12'>No input handling</a>: The PR does not introduce code that handles external inputs; validation and data handling cannot be assessed from the provided changes. <details open><summary>Referred Code</summary> ```txt # ServiceRadar v1.0.68 Docker Compose KV seeding restored and JetStream consumers hardened. ## Whats New **1.0.68** - Restored KV-backed configuration seeding in Docker Compose (including poller stack) so core/agent/poller/zen/db-event-writer bootstrap datasvc and surface in the UI; docs updated accordingly. - Bundled a Compose-ready NATS context inside `serviceradar-tools` for local JetStream/KV inspection without pulling extra images. - Hardened the db-event-writer JetStream consumer with retrying connection/setup logic to survive NATS restarts during Compose bring-up. - Zen now ignores the initial KV watch event when CONFIG_SOURCE=kv to avoid spurious restarts on first sync. ``` </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-12-11 06:46:08 +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/2105#issuecomment-3640484016
Original created: 2025-12-11T06:46:08Z

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/2105#issuecomment-3640484016 Original created: 2025-12-11T06:46:08Z --- ## PR Code Suggestions ✨ No code suggestions found for the PR.