This package builds nostr-rs-relay from source inside the Dockerfile, pinned to an upstream release tag. A bump means pointing the build at a newer tag.
Upstream is developed on sourcehut (git.sr.ht/~gheartsfield/nostr-rs-relay); github.com/scsibug/nostr-rs-relay is a faithful mirror (identical commit SHAs) that the Dockerfile clones from and that is easier to query.
List release tags (sourcehut has no JSON tag API; the GitHub mirror works identically):
git ls-remote --tags --sort=-v:refname https://github.com/scsibug/nostr-rs-relay | grep -v '\^{}$' | head
# canonical home: https://git.sr.ht/~gheartsfield/nostr-rs-relay
The latest release is the highest semver tag. Do not use crates.io — it is frozen at 0.8.12 (Aug 2023) and does not reflect current releases.
-
Dockerfile— setARG NRR_VERSIONto the new tag (e.g.0.10.0) andARG NRR_COMMITto the commit that tag points to. Resolve it with:git ls-remote https://github.com/scsibug/nostr-rs-relay refs/tags/<tag>^{}Use the dereferenced (
^{}) commit. The build fails if the clone's HEAD does not matchNRR_COMMIT. -
startos/versions/current.ts— setversionto<upstream>:0and updatereleaseNotesin every locale. The latest version always lives in this file; edit it in place. Spin off a new version file only when the bump needs anup/downmigration — see Versions. -
Rebuild with
makeand confirm the relay starts.
nostr-rs-relay reads config.toml (modeled in startos/fileModels/config.toml.ts) and runs its own SQLite schema migrations on startup, so a version bump needs no StartOS-side data migration. When bumping, skim the upstream config.toml for any renamed or removed keys the file model writes — additive changes need no action.