Repository navigation
chore(platform): release 2.5.3 (guardrails self-check log mode, OpenTelemetry 1.45.2) - #134
Merged
Merged
Conversation
Importing nemoguardrails.cli sets the root logger to WARNING, after boot.py configured Zelkor logging. Every zelkor-nemo INFO line after startup was dropped, including the guardrail_verdict that log mode promises (#133); warnings still printed. Pin the zelkor-nemo logger to ZELKOR_LOG_LEVEL after the import; the root, and NeMo's own INFO logs that carry user text, stay at WARNING. Verified on a live cluster: verdict lines appear, no prompt text. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…elemetry 1.45.2) PATCH 2.5.3, released together with the 2.5.2 changes (2.5.2 was not tagged): - #133: NeMo self-check input defaults to log (record, never refuse), output off; selfCheck.input/output: block keeps refusing. - #127: OpenTelemetry 1.45.2 / 0.66b2 for CVE-2026-126360. - charts, first-party image tags, Zelkor Dockerfile bases and example charts at 2.5.3; example chart dependencies rebuilt - profiles/values-production.yaml at tag 2.5.3, digests empty until the signed release run - docs/security/cve-log.md: CVE-2026-126360 fixed in v2.5.3-ce - THIRD_PARTY_NOTICES: 2.5.3 row Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
S-gate against the 2.5.3 candidate on the production-shaped lab: 103 tests, 0 failures, 11 environment skips. Default self-check mode (log) for everything except the guardrail-refusal cases (S-12, S-13, S-81, UAT-12, drop-in harmful), which ran under the selfCheck.input: block opt-in. Tool-policy cases (S-71/72/73) ran under a temporary overlay. File paths removed. Fail-closed matrix: PASS 6, GAP 1 (DNS egress). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Release 2.5.3. It carries the 2.5.2 changes, and 2.5.2 itself is not tagged.
log, which records the verdict and never refuses. The output check is off.selfCheck.input/selfCheck.output: blockkeeps refusing.fdfb82b):guardrail_verdictlog lines were dropped on the cluster.zelkor-nemologger is pinned toZELKOR_LOG_LEVEL. The root logger stays at WARNING, so NeMo's own INFO logs, which carry user text, stay out.zelkor-guardrails,zelkor-sidecarandzelkor-aegra.docs/security/cve-log.mdlists it as fixed inv2.5.3-ce.THIRD_PARTY_NOTICEShas a 2.5.3 row. The CE-18 check is unchanged.release-evidence/v2.5.3-ce/.Verification on the production-shaped lab
log)blockopt-inOperational note for the release notes: in
logmode a harmful prompt is no longer stopped after the check, so it costs two provider calls (check plus answer) instead of one. Unpaced bursts reach the CE global per-minute limit sooner.🤖 Generated with Claude Code