Skip to content

chore(deps): russh-keys without OpenSSL; bot terse processing reply#230

Merged
bobleer merged 1 commit intoGCWing:mainfrom
bobleer:chore/russh-keys-no-openssl-bot-verbose-reply
Mar 23, 2026
Merged

chore(deps): russh-keys without OpenSSL; bot terse processing reply#230
bobleer merged 1 commit intoGCWing:mainfrom
bobleer:chore/russh-keys-no-openssl-bot-verbose-reply

Conversation

@bobleer
Copy link
Copy Markdown
Collaborator

@bobleer bobleer commented Mar 23, 2026

Summary

  • Dependencies: Remove the workspace openssl crate and stop enabling openssl on russh-keys for the ssh-remote feature. russh-keys uses its default pure-Rust crypto backend, which simplifies builds (especially on Windows) without pulling optional OpenSSL into this path. Non-Windows git2 still uses vendored-openssl for libgit2 only.
  • WeChat bot: When verbose_mode is off, the immediate "processing your message" reply no longer appends the /cancel_task hint; verbose mode keeps the full message and cancel instructions.

Testing

  • cargo check (full workspace) passes.

- Remove workspace openssl; use russh-keys default (pure-Rust) crypto for ssh-remote
- Git2 on non-Windows still uses vendored-openssl for libgit2 only
- Bot chat: when verbose_mode is off, processing reply omits /cancel_task hint
@bobleer bobleer merged commit 32843f8 into GCWing:main Mar 23, 2026
4 checks passed
@bobleer bobleer deleted the chore/russh-keys-no-openssl-bot-verbose-reply branch March 24, 2026 04:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant