Build(deps-dev): Bump ts-jest from 29.3.1 to 29.4.0#75
Closed
dependabot[bot] wants to merge 1 commit intomainfrom
Closed
Build(deps-dev): Bump ts-jest from 29.3.1 to 29.4.0#75dependabot[bot] wants to merge 1 commit intomainfrom
dependabot[bot] wants to merge 1 commit intomainfrom
Conversation
Bumps [ts-jest](https://github.com/kulshekhar/ts-jest) from 29.3.1 to 29.4.0. - [Release notes](https://github.com/kulshekhar/ts-jest/releases) - [Changelog](https://github.com/kulshekhar/ts-jest/blob/main/CHANGELOG.md) - [Commits](kulshekhar/ts-jest@v29.3.1...v29.4.0) --- updated-dependencies: - dependency-name: ts-jest dependency-version: 29.4.0 dependency-type: direct:development update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
Contributor
Author
|
The |
Contributor
Author
|
Superseded by #101. |
joelteply
added a commit
that referenced
this pull request
Apr 24, 2026
Vision AI (qwen2-vl-7b) was emitting the literal string "Sentinel/coding-agent" as its response to image attachments. Reproduced on both Mac (in-process llamacpp + Metal) and Linux/CUDA (DMR) — platform-independent. Root cause: SentinelAwarenessSource was injecting a 15KB block of sentinel pipeline + tool definitions + <tool_use> XML examples into EVERY persona's system prompt regardless of model capability. qwen2-vl declares capabilities [text-generation, chat, vision, streaming] with NO tool-use — confronted with a "sentinel/coding-agent: Launch Claude Code..." line in the prompt, the VLM imitated the only tool-name token sequence it saw and produced "Sentinel/coding-agent" as text output. Two surgical changes: 1. SentinelAwarenessSource.isApplicable: skip when toolCapability === 'none'. ToolDefinitionsSource and ToolMethodologySource already gate this way; sentinels are tools-as-pipelines so the same capability boundary applies. 2. PersonaResponseGenerator.buildRagContext: derive toolCapability from the registry-resolved capabilities (no 'tool-use' cap → 'none') instead of defaulting to 'xml' for every non-native-tool provider. Capability declaration travels WITH the request — registry truth, not provider-string defaults. Validated end-to-end on Mac (in-process llamacpp + Metal): pre-fix Vision AI reply: "Sentinel/coding-agent" post-fix Vision AI reply: "The image shows a single red brick with three circular holes on its surface. The brick is positioned on a wooden surface, which appears to be a table or workbench. The background seems to be an indoor setting, possibly a workshop or construction site." Bigmama-wsl reproduced the bug on Linux/CUDA Carl path (image-0.png → '<tool_use><tool_name>interface/screenshot</tool_name>...' garbage from Vision AI), confirming it's not platform-specific and confirming the fix needs to land in the docker images for merge. Test command: ./jtag collaboration/chat/send --room=general --media=test-data/images/image-0.png --message='Vision AI — what is in this image?' Verification: ./jtag collaboration/chat/export --room=General --limit=15 Pre-push hook fix (src/scripts/git-prepush.sh): - Source scripts/shared/cargo-features.sh in Phase 2 + Phase 3 so cargo check and cargo test --lib pass `--features metal,accelerate` on Mac. Without this, the compile_error guard added in 7f32bc0 (Mac builds without --features metal forbidden) makes the pre-push hook unrunnable on Mac. Same single-source-of-truth path npm start uses. ESLint baseline bump (src/eslint-baseline.txt 6502 → 6520): - Pre-existing repo state was 6532 errors before this commit; this commit reduces to 6520 (-12 from net cleanup of unused imports in PRG.ts + SentinelAwarenessSource.ts). Baseline file was stale at 6502 from an earlier commit; updating to current real state at 6520. Future pushes only fail if they regress beyond 6520. Per the hook's own guidance: "the baseline should track real state." Closes the vision arm of task #75.
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.
Bumps ts-jest from 29.3.1 to 29.4.0.
Release notes
Sourced from ts-jest's releases.
Changelog
Sourced from ts-jest's changelog.
Commits
f692f74chore(release): 29.4.084e093efeat: support Jest 302d6fe5cbuild(deps): Update dependency eslint-plugin-jsdoc to ^50.8.083c6d35build(deps): Update dependency eslint-plugin-jest to ^28.13.394797d0build(deps): Update dependency@vitejs/plugin-react-swcto ^3.10.29a9bd5cbuild(deps): Update ESLint packages to ^8.34.0cbd81fdbuild(deps): Update dependency eslint-plugin-jest to ^28.13.01d3fb0dbuild(deps): Update dependency@types/nodeto v20.19.032efecbbuild(deps): Update docusaurus monorepo to ^3.8.15133d48build: upgradedocusaurusto 3.8Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)