Skip to content

Build(deps-dev): Bump ts-jest from 29.3.1 to 29.4.0#75

Closed
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/npm_and_yarn/ts-jest-29.4.0
Closed

Build(deps-dev): Bump ts-jest from 29.3.1 to 29.4.0#75
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/npm_and_yarn/ts-jest-29.4.0

Conversation

@dependabot
Copy link
Copy Markdown
Contributor

@dependabot dependabot Bot commented on behalf of github Jun 16, 2025

Bumps ts-jest from 29.3.1 to 29.4.0.

Release notes

Sourced from ts-jest's releases.

v29.4.0

Please refer to CHANGELOG.md for details.

v29.3.4

Please refer to CHANGELOG.md for details.

v29.3.3

Please refer to CHANGELOG.md for details.

v29.3.2

Please refer to CHANGELOG.md for details.

Changelog

Sourced from ts-jest's changelog.

29.4.0 (2025-06-11)

Features

29.3.4 (2025-05-16)

Bug Fixes

  • fix: fix TsJestTransformerOptions type (3b11e29), closes #4247
  • fix(cli): fix wrong path for preset creator fns (249eb2c)
  • fix(config): disable rewriteRelativeImportExtensions always (9b1f472), closes #4855

29.3.3 (2025-05-14)

Bug Fixes

  • fix(cli): init config with preset creator functions (cdd3039), closes #4840
  • fix(config): disable isolatedDeclarations (5d6b35f), closes #4847

29.3.2 (2025-04-12)

Bug Fixes

  • fix: transpile js files from node_modules whenever Jest asks (968370e), closes #4637
Commits
  • f692f74 chore(release): 29.4.0
  • 84e093e feat: support Jest 30
  • 2d6fe5c build(deps): Update dependency eslint-plugin-jsdoc to ^50.8.0
  • 83c6d35 build(deps): Update dependency eslint-plugin-jest to ^28.13.3
  • 94797d0 build(deps): Update dependency @​vitejs/plugin-react-swc to ^3.10.2
  • 9a9bd5c build(deps): Update ESLint packages to ^8.34.0
  • cbd81fd build(deps): Update dependency eslint-plugin-jest to ^28.13.0
  • 1d3fb0d build(deps): Update dependency @​types/node to v20.19.0
  • 32efecb build(deps): Update docusaurus monorepo to ^3.8.1
  • 5133d48 build: upgrade docusaurus to 3.8
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot 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 rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

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>
@dependabot @github
Copy link
Copy Markdown
Contributor Author

dependabot Bot commented on behalf of github Jun 16, 2025

The reviewers field in the dependabot.yml file will be removed soon. Please use the code owners file to specify reviewers for Dependabot PRs. For more information, see this blog post.

@dependabot dependabot Bot requested a review from joelteply June 16, 2025 22:49
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Jun 16, 2025
@dependabot @github
Copy link
Copy Markdown
Contributor Author

dependabot Bot commented on behalf of github Aug 5, 2025

Superseded by #101.

@dependabot dependabot Bot closed this Aug 5, 2025
@dependabot dependabot Bot deleted the dependabot/npm_and_yarn/ts-jest-29.4.0 branch August 5, 2025 04:01
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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants