chore(deps): update dependency sheeki03/tirith to v0.3.1#265
Merged
Conversation
Signed-off-by: Renovate Bot <renovate@whitesourcesoftware.com>
donbeave
added a commit
that referenced
this pull request
May 18, 2026
Bump `TIRITH_VERSION` from 0.2.12 to 0.3.1 in `docker/construct/versions.env`. Upstream 0.3.1 fixes an AWS access-key false-positive in S3 pre-signed URLs and SigV4 Authorization headers — the credential rule no longer flags `AKIA…` matches that sit inside actual SigV4 fields with non-empty signatures, while bare access keys and non-SigV4 contexts continue to fire. This is the first Renovate-driven update produced by the customManagers added in #256, so it also doubles as a smoke test of that automation. Signed-off-by: Renovate Bot <renovate@whitesourcesoftware.com> Signed-off-by: Alexey Zhokhov <alexey@zhokhov.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.
This PR contains the following updates:
0.2.12→0.3.1Release Notes
sheeki03/tirith (sheeki03/tirith)
v0.3.1Compare Source
Fixed
AKIA…matches that sit inside theX-Amz-Credentialvalue of a parseable URL whose query also hasX-Amz-Algorithm=AWS4-HMAC-SHA256and a non-emptyX-Amz-Signature, or inside theCredential=field of anAuthorization: AWS4-HMAC-SHA256 …, Signature=…header. The carve-out is anchored to absolute byte spans of the actual SigV4 fields — a strayAKIA…elsewhere in the same URL/headers/body still fires. Bare access keys,Authorization: Bearer AKIA…without SigV4 markers, and URLs missing any SigV4 marker continue to flag. New tests cover each shape and each adversarial bypass we considered.tirith setup codexagainst current Codex CLI versions — recognises the newError: No MCP server named 'X' found.stderr message instead of treating it as an unexpected failure, and accepts both the legacy top-levelcommand/argsJSON shape and the current nestedtransport.command/argsshape returned bycodex mcp get --json. Drift detection still works against either shape.zsh -lc ...no longer blocked by stale.zshenvguard — the guard now bakes a stable absolute path to the tirith binary at install time (resolved via PATH lookup with symlink canonicalisation, falling back tocurrent_exe()when the PATH entry is a#!wrapper script for npm/pnpm). Previously the guard relied on the bare nametirithbeing on PATH, which fails before.zshrc/.zprofilepopulate PATH. The path is shell-quoted so spaces and apostrophes round-trip safely.tirith doctor/tirith init(#105) — Unix install via npm no longer warns that thenode_modules/tirith/bin/tirithJS wrapper shadows the native binary.resolve_effective_tirith_targetnow detects the npm wrapper layout (after canonicalising the PATH entry through any symlinks), looks up the matching@sheeki03/tirith-{platform}-{arch}/bin/tirithsibling using the same OS+arch mapping the wrapper itself uses, and treats both paths as the same install. Unrelated tirith binaries on PATH (the documented PyPI collision case) still warn.tirith doctor/tirith initno longer warn that the Scoop shim at~\scoop\shims\tirith.exeshadows the real binary; the shim is resolved through its.shimsidecar to the real path before the equality check.verify_sha256portability —scripts/install.shnow probes whethersha256sum -creads from stdin and falls back toshasum -a 256 -cwhen not (some BSDs, busybox). Regression harness added.Security
randbumped to 0.9.3 (RUSTSEC-2026-0097).rustls-webpkibumped to a version unaffected by upstream advisories.Docs
Internal
maininstead of opening auto-merge PRs that silently no-op'd when no required checks were present, accumulating an unmerged backlog.#[cfg(windows)]to silence a clippy warning surfaced by recent toolchain versions._tirith_outputin the bash, fish, and zsh hooks now forwards all arguments instead of only$1/$argv[1]. No call site passes more than one argument today, but the previous form was a footgun for any future refactor that splits a multi-line message across positional arguments.v0.3.0Compare Source
Added
TIRITH_BASH_PREEXEC_ENFORCE=1to get real blocking in bash preexec mode viashopt -s extdebugplusreturn 1from theDEBUGtrap. Whole-line fail-closed semantics; one block verdict skips the entire typed line. Install-time hostile-history check refuses to engage in shells whereHISTCONTROLcontainsignorespace/ignoredups/ignoreboth, anyHISTIGNOREis set, or history is disabled. Runtime drift detection with cache-then-degrade downgrades the session to warn-only rather than claim protection it cannot deliver. IdempotentDEBUGtrap trampoline chains through any pre-existing userDEBUGtrap. Closes the "tirith says BLOCKED but the command executes" gap in #77.tirith doctorlive state — bash hook now exportsTIRITH_BASH_EFFECTIVE_MODEandTIRITH_BASH_EFFECTIVE_PROTECTION(interactive shells only) sodoctor, a child process, can read the parent shell's live state. Doctor splits requested-vs-effective onto separate lines so mid-session degrades are legible.tirith threatdbsubcommand, threat DB compiler binary with CI workflow, signed cache format, detection rules keyed on known-bad hostnames/IPs/packages/typosquats, supplemental feed overlay with Phase B feed parsers and rule mapping, Phase C runtime API enrichment wired intocheckand daemon paths, auto-update and staleness reporting indoctor.tirith warningsCLI command and shell exit summaries across all hooks.WarnAckexit code 3.tirith policy init,validate,testsubcommands;tirith explain --rulefor rule documentation.tirith doctor --fixfor progressive remediation, plus--reset-bash-safe-modeflag.tirith setupgainscopilot-cli(#74) andkiro(#75); scanner recognises.kiro/,.amazonq/cli-agents/, and.github/hooks/as config paths.--include,--exclude,--profilescan filters.tirith doctor.SKILL.mdfor AI agent discovery.confirmhelper, normalised output flags, help examples on every subcommand.aarch64-unknown-linux-musltarget in the release pipeline.Fixed
TIRITH=0pipe bypass without weakening paste safety (#78).host:/pathno longer trips URL-host false positives (#26).sudo,env,doas,command,time,nohupprefixes) now resolve throughresolve_wrapped_commandin thenetwork_denypath so prefix chains cannot bypass policy.codefilebyte slicing clamps to UTF-8 char boundaries to avoid a panic on non-ASCII code (#76)./tmpleaks (#80).HISTCONTROLbypass; preexec cache key corrected so drift-triggering pipelines do not leak composite rules.Changed
fuzz/targetandCargo.lockignored in CI path filters.docs/troubleshooting.mdupdated for the new enforcement matrix, threat-intel features, escalation, hidden findings,--formatflag canonicalisation, and new MCP client setup guides (Gemini CLI, OpenClaw, Pi CLI).Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate.