Repository navigation
build(deps): bump russh from 0.65.0 to 0.65.1 in the cargo group across 1 directory - #31
Closed
dependabot[bot] wants to merge 1 commit into
Closed
dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps the cargo group with 1 update in the / directory: [russh](https://github.com/warp-tech/russh). Updates `russh` from 0.65.0 to 0.65.1 - [Release notes](https://github.com/warp-tech/russh/releases) - [Commits](Eugeny/russh@v0.65.0...v0.65.1) --- updated-dependencies: - dependency-name: russh dependency-version: 0.65.1 dependency-type: direct:production dependency-group: cargo ... Signed-off-by: dependabot[bot] <support@github.com>
fadion
added a commit
that referenced
this pull request
Nov 19, 2026
Clears GHSA-736f-c93q-9fwx (an agent could sign after being locked) and GHSA-9264-jvgf-6w2f (kex_done ran before host-key verification). Neither reaches Schemaic: it uses only russh's agent client, and its SSH handler does not implement kex_done. Bumped anyway so a future handler cannot inherit the flaw. The lock moves a few crates' windows-sys/getrandom edges to versions already in it. That is cargo's own re-resolution for russh 0.65.1's changed dependencies, not stray churn: a lock with only the russh entry edited is rejected under --locked. No package is added or changes version besides russh. Supersedes #31.
fadion
added a commit
that referenced
this pull request
Nov 19, 2026
Rust 1.100's clippy adds needless_bool for an `if … { return false }
true` tail, and CI fails on it under -D warnings. Red: the lint job
failed on exactly this line (ddl.rs:15853) on the unfixed tree in #31's
run, and the local 1.100 clippy is clean after it. Same predicate,
rewritten as one expression.
fadion
added a commit
that referenced
this pull request
Nov 19, 2026
16.16 adds binary_upgrade_set_next_attribute_versions(pg_lsn[]) (upstream 0c8ffa1ad2), and CI's postgres:16 image now reports it, so the live catalog tests failed: the typo checker would squiggle it and autocomplete would never offer it. The entry is written from pg_proc.dat by the module's three rules, and added to PG_FUNCTIONS and PG_SUGGESTED in sorted position. Red: every_function_the_server_reports_is_in_the_catalog and the_offered_subset_is_still_what_the_filter_answers failed in #31's live run on the unfixed tree. They cannot be run red or green here: the local server is 16.15, which lacks the function, so green is CI's call.
Owner
|
Superseded by 5312ea4 on main, which makes the same russh 0.65.1 bump together with the two CI fixes this run tripped on (Rust 1.100's needless_bool lint, PostgreSQL 16.16's new builtin). |
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 the cargo group with 1 update in the / directory: russh.
Updates
russhfrom 0.65.0 to 0.65.1Release notes
Sourced from russh's releases.
Commits
b33092av0.65.120c5a93fix(keys): keep the comment when loading a public key file (#801)3a21566fix(client): accept non-canonical ECDSA P-521 signature mpints after strict d...a6be9bafix(cipher): count the MAC tag in the minimum packet length check (#802)43a46d6fix(AgentClient): propagate method errors (#808)56384e6add Eric-D as a contributor for code (#799)7c59594fix(server): let Dropbear through strict kex by accounting for the ignored fi...d10345ddeps: trim aws-lc-rs features to avoid transitive deps (#809)0a8cc28deps: remove dep on generic-array 0.14 compat (#810)92562d3tests: adapt to VerifiedPublicKey after #785 (#807)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 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 <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditionsYou can disable automated security fix PRs for this repo from the Security Alerts page.