cameri/nostream nostream@3.10.0

on GitHub

Minor Changes

• #922 fcb33de Thanks @Priyanshubhartistm! - feat(payments): add per-plan event rate limits and retention

Patch Changes

• #1009 ad8c5c4 Thanks @chappie-daemon! - build: pin the node base image in every file that names one

  Dockerfile pinned node:24.22.1-alpine by digest, but Dockerfile.railwayapp, Dockerfile.test, docker-compose.yml and test/integration/docker-compose.yml still said node:24-alpine. The relay image, the CI image, the Railway image and both migration containers could each start from a different base, and a floating tag moves under a release — so the same commit built twice could run different node code without a change saying so.

  All five now carry the same tag and digest, and a unit test holds them there: it fails if any reference loses its digest, and it fails if two different references appear.

• #1010 fa54cb0 Thanks @chappie-daemon! - fix(settings): state that rate-limit periods are milliseconds and reject a period that is not one

  Every shipped limit counts in milliseconds — 1000, 60000, 900000, 3600000 — but nothing said so. RateLimit.period is a bare number, so an operator writing period: 60 for a minute got a 60 ms window — and because rate is hits per window, that is a limit a thousand times looser than intended, honoured without complaint, and caught by nothing.

  The unit is now stated on RateLimit and on every rateLimits block in resources/default-settings.yaml, and validateRateLimitPeriods rejects what cannot be a count of milliseconds: a fraction, a string, a non-number, or anything below one millisecond. A whole number is not enough to tell 60 from 60000, which is why the unit is documented where it is set.