Skip to content

docs: link the ePHPm releases page instead of naming the current release #6

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
luthermonson merged 1 commit into from
Oct 27, 2026
Merged

docs: link the ePHPm releases page instead of naming the current release #6

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 1 addition & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -53,8 +53,7 @@ written in Rust.
- **The ePHPm runtime** — any tagged release works for the core
commands (the `ephpm_kv_*` SAPI functions have shipped since ePHPm
v0.1.0; `FLUSHDB`/`FLUSHALL` need `ephpm_kv_flush_all()`, added in
v0.1.2; `SETNX` / `SET … NX` need `ephpm_kv_setnx()`; current release:
v0.10.2). The hash, multi-key and other commands listed under
v0.1.2; `SETNX` / `SET … NX` need `ephpm_kv_setnx()`; see the [ePHPm releases](https://github.com/ephpm/ephpm/releases) for the latest version). The hash, multi-key and other commands listed under
[ePHPm v0.13+ commands](#ephpm-v013-commands) need ePHPm **v0.13.0+**;
each is feature-detected, so on an older runtime those commands keep
raising `CommandNotSupportedException` exactly as before. The functions are
Expand Down
Loading