Repository navigation
chore(deps): bump rustls from 0.23.45 to 0.23.46 in /bots/finishingbot - #637
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [rustls](https://github.com/rustls/rustls) from 0.23.45 to 0.23.46. - [Release notes](https://github.com/rustls/rustls/releases) - [Changelog](https://github.com/rustls/rustls/blob/main/CHANGELOG.md) - [Commits](rustls/rustls@v/0.23.45...v/0.23.46) --- updated-dependencies: - dependency-name: rustls dependency-version: 0.23.46 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
|
Important Review skippedBot user detected. To trigger a single review, invoke the
|
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
## Problem The shared Idris dependent scanner test fixture no longer initializes `Mock.responses`. Rust rejects the integration test with E0063 at `tests/scan_tests.rs:352`, so all-target compilation and the following tests cannot run. The same defect is present on current main and blocks dependency PRs #633–#637. Actual failure: [job 124701176251](https://github.com/hyperpolymath/gitbot-fleet/actions/runs/41256667603/job/124701176251), with the same current-main failure in job 124813337915. ## Change Initialize the existing response override map with `BTreeMap::new()` in `ready_mock`. This is one source line; the real transport, assertions, dependency locks and vendored bot sources are unchanged. ## Verification The source and exact Git blob were inspected, and the one-line diff was read back. No local Rust execution is claimed. The existing `idris-dependents` hosted matrix must qualify this revision using its locked all-target build, tests, Clippy and formatting gates. The older E2E closure defect has a separate fix already on main (#639). Echidnabot's vendored source pin, existing governance/security findings and dependency updates need their own verified dispositions; this PR does not suppress them. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> <!-- coderabbit-ai-generated:v1 --> ## Summary by CodeRabbit * **Tests** * Updated automated test setup to allow tests to provide custom mock responses while retaining the existing default mock behavior. This change affects test coverage and does not alter functionality available in the application. <!-- end of auto-generated comment: release notes by coderabbit.ai --> ## Hosted follow-up The da53 hosted locked build passed the original missing-field failure, then the existing edge-case suite exposed two stale assertions in job126927683205/run41931039453. Current412bcad784dd16193475a09ecfa614147dc6fa51 keeps hard-error rejection by using HTTP500 for that fixture (404 is intentionally recorded as a skipped URL), and includes the already public skippedUrls field in the exact JSON assertion. Existing scan_tests already exercises both raw paths for skipped404/410/451 and hard401/403/422/429/500/503; production behavior is unchanged. Current412 requires its own full hosted result. Separate governance failures—canonical action allowlist, retained Python audit/test implementations and the older scanner/native-lock contract—remain open and are not waived by this test repair. The vendored Echidnabot dependency PR also needs its upstream source closure resolved independently.



Bumps rustls from 0.23.45 to 0.23.46.
Commits
f04804fDelay saving KX hint until handshake confirmation049d39bBump version to 0.23.466d0ba08Eliminate secret from impl Debug forServerSessionValue2b82b81unbuffered: update TLS 1.3 traffic keys before exhausting them74343e7conn: update TLS 1.3 traffic keys within fragmented writes795eea7Advance the HPKE sequence only after seal succeedsd67cb71stream: provide backpressure while buffering received plaintext7a69adeutil: fuse flushes from connections with errors493d089conn: fuse writes for connections with errorsdb00e01util: keep flushing after short writesDependabot 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 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)You can disable automated security fix PRs for this repo from the Security Alerts page.