chore(deps): bump predicates from 3.1.3 to 3.1.4 in /codex-rs

[dependabot]

Bumps predicates from 3.1.3 to 3.1.4.

Changelog

Sourced from predicates's changelog.

[3.1.4] - 2026-02-11

• Make BoxPredicate::find_case use the inner find_case implementation

Commits

• f54f2cd chore: Release
• ce8099e Merge pull request #200 from rynoV/master
• 34d11de docs: Update changelog
• a03ae99 feat: Make BoxPredicate::find_case use the inner find_case
• 9b59897 test: Add test for BoxPredicate::find_case
• 45f4333 Merge pull request #201 from assert-rs/renovate/crate-ci-typos-1.x
• b9c965b chore(deps): Update pre-commit hook crate-ci/typos to v1.42.3
• 0d9cf08 Merge pull request #199 from epage/template
• 9968b8a chore: Update from _rust template
• e4f2b35 chore(ci): Update action
• Additional commits viewable in compare view

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 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)

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}

[andrei-hasna]

[REVIEW] NO_GO — #483 @ 7ca3d02 — lens: correctness+security+gates, reviewer unresolved-account001 (1 of 1)

Candidate read:

• git log --oneline origin/main..HEAD — exit 0; one commit, the predicates 3.1.3 to 3.1.4 bump.
• git diff origin/main...HEAD --stat — exit 0; 1 file changed, 2 insertions, 2 deletions.
• Full diff of codex-rs/Cargo.lock, plus surrounding lock entries, codex-rs/Cargo.toml, and the codex-cli, codex-exec, and codex-core dev-dependency declarations and test consumers. The dependency remains test-only and its dependency list is unchanged.
• Confirmed origin/main is 06ff792 and the reviewed head is 7ca3d02.

Setup and declared gates:

• bun install — exit 0; setup only, not a repo gate; 521 packages installed.
• The root package.json declares no typecheck script.
• The root package.json declares no test script, so this repo declares no test gate. No substitute local test command was invented.
• gh pr view 483 --repo hasna/codewith --json statusCheckRollup — exit 0; 26 checks read: 9 success, 1 failure, 3 skipped, 13 in progress.

Authoritative forge checks read by name and conclusion:

• Bazel test on ubuntu-24.04 for x86_64-unknown-linux-gnu — FAILURE
• Build Codewith Linux CLI — IN_PROGRESS
• cla — SUCCESS
• Check for spelling errors — SUCCESS
• Blob size policy — SUCCESS
• cargo-deny — SUCCESS
• build-test — SUCCESS
• Detect changed areas — SUCCESS
• python-sdk — SUCCESS
• Bazel test on ubuntu-24.04 for x86_64-unknown-linux-musl — IN_PROGRESS
• Bazel test on windows-latest for x86_64-pc-windows-gnullvm shard 1/4 — IN_PROGRESS
• sdks — IN_PROGRESS
• Format / etc — SUCCESS
• Bazel test on windows-latest for x86_64-pc-windows-gnullvm shard 2/4 — IN_PROGRESS
• Bazel test on windows-latest for x86_64-pc-windows-gnullvm shard 3/4 — IN_PROGRESS
• Bazel test on windows-latest for x86_64-pc-windows-gnullvm shard 4/4 — IN_PROGRESS
• Bazel test on windows-latest for x86_64-pc-windows-gnullvm (native main) — SKIPPED
• cargo shear — SUCCESS
• Bazel clippy on ubuntu-24.04 for x86_64-unknown-linux-gnu — IN_PROGRESS
• Argument comment lint package — SKIPPED
• Bazel clippy on windows-latest for x86_64-pc-windows-gnullvm — IN_PROGRESS
• Verify release build on ubuntu-24.04 for x86_64-unknown-linux-gnu — IN_PROGRESS
• Argument comment lint - Linux — IN_PROGRESS
• Verify release build on windows-latest for x86_64-pc-windows-gnullvm — IN_PROGRESS
• Argument comment lint - Windows — IN_PROGRESS
• [code]smith — SKIPPED

Blocking P0/P1 finding:

• P1 required compatibility gate: Bazel test on ubuntu-24.04 for x86_64-unknown-linux-gnu fails at the reviewed head because MODULE.bazel.lock was not refreshed after codex-rs/Cargo.lock changed. The job log states MODULE.bazel.lock is out of date and requires just bazel-lock-update. This is currently reachable and candidate-caused. Remedy: regenerate and commit MODULE.bazel.lock, then let the authoritative checks run on the new head.

Security/correctness review found no separate reachable P0/P1 defect. No secrets, auth, sandbox, command execution, or session-integrity surface is changed by this lockfile-only test dependency bump.

Non-blocking follow-ups: none.

[andrei-hasna]

[REVIEW-FIX] Resolved the live Bazel lock blocker on commit 6368e56.

• Regenerated MODULE.bazel.lock for predicates_3.1.4; the only generated diff is the expected 3.1.3 to 3.1.4 metadata-key update.
• bazel mod deps --lockfile_mode=update — exit 0.
• scripts/check-module-bazel-lock.sh — exit 0.
• shield review on the staged one-file fix — exit 0, no security issues found.
• Commit provenance ends with Agent: unresolved-account001.

The previous NO_GO names 7ca3d02 and is stale against the new head. Focused re-review is limited to this named lock defect and direct regressions; a GO will follow only after the authoritative forge checks on 6368e56 are green.

[andrei-hasna]

[REVIEW] GO — #483 @ 6368e56 — lens: correctness+security+gates, reviewer unresolved-account001 (1 of 1)

Focused re-review result:

• The named P1 Bazel lock defect is fixed. MODULE.bazel.lock now changes only the expected metadata key from predicates_3.1.3 to predicates_3.1.4; no unrelated dependency metadata moved.
• No direct regression from that fix was found.
• Blocking P0/P1 findings: none.
• Non-blocking follow-ups: none.

Commands and exact exit evidence:

• bun install — exit 0; setup only, not a repo gate; 521 packages installed.
• just bazel-lock-update — exit 127 because just is not installed on this lane; no generator ran through that wrapper.
• THE LANE'S CHOSEN COMMAND: bazel mod deps --lockfile_mode=update, the exact body of the repo recipe — exit 0; generated the one-line Bazel lock metadata update. This is supplemental remediation evidence, not an invented package.json gate.
• THE LANE'S CHOSEN COMMAND: scripts/check-module-bazel-lock.sh — exit 0; focused supplemental verification of the named defect, not an invented package.json gate.
• shield review with the one-file fix staged — exit 0; 1 changed file checked, 0 security issues.
• gh pr view 483 --repo hasna/codewith --json statusCheckRollup — exit 0; 43 authoritative checks read: 40 SUCCESS, 0 FAILURE, 3 SKIPPED, 0 pending.

Declared gate statement:

• The root package.json declares no typecheck script.
• The root package.json declares no test script, so this repo declares no test gate. No substitute local test command was treated as the repo's test gate.

Authoritative forge checks read by name and conclusion at 6368e56:

• Bazel test on ubuntu-24.04 for x86_64-unknown-linux-gnu — SUCCESS
• cla — SUCCESS
• Check for spelling errors — SUCCESS
• Blob size policy — SUCCESS
• cargo-deny — SUCCESS
• build-test — SUCCESS
• Build Codewith Linux CLI — SUCCESS
• Detect changed areas — SUCCESS
• python-sdk — SUCCESS
• metadata — SUCCESS
• Bazel test on ubuntu-24.04 for x86_64-unknown-linux-musl — SUCCESS
• Bazel test on windows-latest for x86_64-pc-windows-gnullvm shard 1/4 — SUCCESS
• Format / etc — SUCCESS
• sdks — SUCCESS
• Build release x86_64-unknown-linux-gnu — SUCCESS
• Bazel test on windows-latest for x86_64-pc-windows-gnullvm shard 2/4 — SUCCESS
• Build ptrcomp-sandbox x86_64-unknown-linux-gnu — SUCCESS
• Bazel test on windows-latest for x86_64-pc-windows-gnullvm shard 3/4 — SUCCESS
• Build release aarch64-unknown-linux-gnu — SUCCESS
• Bazel test on windows-latest for x86_64-pc-windows-gnullvm shard 4/4 — SUCCESS
• Build ptrcomp-sandbox aarch64-unknown-linux-gnu — SUCCESS
• Build release x86_64-apple-darwin — SUCCESS
• Build ptrcomp-sandbox x86_64-apple-darwin — SUCCESS
• Build release aarch64-apple-darwin — SUCCESS
• Build ptrcomp-sandbox aarch64-apple-darwin — SUCCESS
• Build release x86_64-unknown-linux-musl — SUCCESS
• Build ptrcomp-sandbox x86_64-unknown-linux-musl — SUCCESS
• Build release aarch64-unknown-linux-musl — SUCCESS
• Build ptrcomp-sandbox aarch64-unknown-linux-musl — SUCCESS
• Bazel test on windows-latest for x86_64-pc-windows-gnullvm (native main) — SKIPPED
• cargo shear — SUCCESS
• Build ptrcomp-sandbox x86_64-pc-windows-msvc from source — SUCCESS
• Build ptrcomp-sandbox aarch64-pc-windows-msvc from source — SUCCESS
• Argument comment lint package — SKIPPED
• Bazel clippy on ubuntu-24.04 for x86_64-unknown-linux-gnu — SUCCESS
• Bazel clippy on windows-latest for x86_64-pc-windows-gnullvm — SUCCESS
• Verify release build on ubuntu-24.04 for x86_64-unknown-linux-gnu — SUCCESS
• Argument comment lint - Linux — SUCCESS
• Verify release build on windows-latest for x86_64-pc-windows-gnullvm — SUCCESS
• Argument comment lint - Windows — SUCCESS
• Bazel test on windows-latest for x86_64-pc-windows-gnullvm — SUCCESS
• CI results (required) — SUCCESS
• [code]smith — SKIPPED

Disposition: GO. The previous NO_GO was for 7ca3d02 and is stale; the current exact head has the named blocker fixed and all authoritative forge checks terminal without failure.