This bumps session-rs from 0.2.0 to 0.2.1, in both Cargo.toml (so builds can't pick up 0.2.0) and Cargo.lock. There are no code changes.
0.2.1 fixes a memory leak: each connection's handlers held a clone of its Session, and the Session held the handlers, so neither was ever freed after a disconnect (selimaj-dev/session-rs#2).
Testing
cargo build has no warnings.
Local smoke test:
/health returns ok.
Three connections in a row each got correct responses to get_player and an unknown method.
## Summary
This bumps `session-rs` from 0.2.0 to 0.2.1, in both `Cargo.toml` (so builds can't pick up 0.2.0) and `Cargo.lock`. There are no code changes.
0.2.1 fixes a memory leak: each connection's handlers held a clone of its `Session`, and the `Session` held the handlers, so neither was ever freed after a disconnect (selimaj-dev/session-rs#2).
## Testing
- `cargo build` has no warnings.
- Local smoke test:
- `/health` returns `ok`.
- Three connections in a row each got correct responses to `get_player` and an unknown method.
- SIGTERM shuts the server down cleanly.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Picks up the fix that releases session handlers on close, so closed
connections no longer leak their Session and handler state.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
This bumps
session-rsfrom 0.2.0 to 0.2.1, in bothCargo.toml(so builds can't pick up 0.2.0) andCargo.lock. There are no code changes.0.2.1 fixes a memory leak: each connection's handlers held a clone of its
Session, and theSessionheld the handlers, so neither was ever freed after a disconnect (selimaj-dev/session-rs#2).Testing
cargo buildhas no warnings./healthreturnsok.get_playerand an unknown method.🤖 Generated with Claude Code