github getnora-io/nora v1.4.7

51 minutes ago

[1.4.7] - 2026-11-18

Changed

  • nora gc --apply and nora retention-apply --yes warn when a server runs on the same storage (#988) — the commands take their own publish locks, not the server's, so their deletions are not serialized with the server's publishes, and the admin guide did not say whether the server should be stopped first. Before deleting, they now print one line on stderr when a server is running on the storage, and say how to run them safely: with the server stopped, or through the server's own [gc] / [retention] schedule. On local storage the check tests the lock each server holds on its .nora-staging/ directory from start to exit, so the staging a crashed server left behind does not warn; an object store keeps no such lock, so on S3 and GCS the commands always say they cannot tell. The commands still run: this is a warning, not a refusal. Dry runs print nothing new. The admin guide (section 5.3) now says when to use the commands and when to rely on the server's schedule, and drops the nora gc --dry-run flag that never existed.
  • NORA's own date code moves off chrono (#1282) — chrono is marked unmaintained (RUSTSEC-2026-0543). Every date NORA writes or reads now goes through one module on the time crate, which was already in the dependency tree, so the build pulls in no new crate. Nothing changes on the wire or in storage: the audit log, activity feed, backup metadata, Docker token issued_at, Last-Modified of raw files and Composer documents, apt Release dates, Maven lastUpdated and Composer upload times are written byte for byte as before, and upstream dates (npm time, PyPI, NuGet published, Go, Cargo, Conan, Pub, Ansible, Terraform, RubyGems, Composer) and stored backup metadata are read with the same leniency, including RFC 3339 with a space or lower-case t, offsets without a colon, leap seconds and fractions longer than nine digits. Golden tests pin each spelling, and a corpus of 5273 date strings pins what the parsers made of them before the change. nora-registry no longer depends on chrono itself; it stays in the tree only through object_store, and deny.toml keeps the advisory accepted for that reason.
  • Two builds of one commit give the same binary (#1301) — the allocator's C code embedded the build's date and time, so two builds of the same source differed in a few bytes and a release asset could not be checked by building it again. The Dockerfile now fixes that clock (SOURCE_DATE_EPOCH), and building the binary target from a release tag gives the same bytes on every run.

Fixed

  • An npm packument the upstream confirms is no longer written again on object storage (#1064) — when a cached packument's TTL had expired and the upstream answered 304 Not Modified, NORA read the whole packument from storage twice and wrote it back, only to move the body's modification time, which the freshness check read. On object storage every such revalidation downloaded and re-uploaded the body. A 304 now reads the body once and writes only the small validator sidecar, which records when the upstream last confirmed the copy, and freshness is read from there. A copy without such a record keeps the body's write time as before, and an upstream that stops sending validators leaves no stale record behind. The release age that curation falls back to for a version the first-seen ledger does not list is read as before. The responses are byte-for-byte the same.
  • Maven retention no longer leaves a retired SNAPSHOT listed in two corner cases (#1291) — the fix for #1281 left two cases as they were in 1.4.5. A proxy fetch of a SNAPSHOT's version-level maven-metadata.xml that ran while retention removed that document could leave the document's checksums behind without the document. And an artifact whose id looks like a version of another artifact, such as com.example.lib:1.0-SNAPSHOT next to com.example:lib, kept the other artifact's version listed: after retention removed com.example:lib:1.0-SNAPSHOT, its maven-metadata.xml still listed the SNAPSHOT, and <latest> could name it, because the files under com/example/lib/1.0-SNAPSHOT/2.0/ were counted as files of that version. The proxy fetch now writes a version-level document and its checksums under the artifact's lock, the lock retention takes to remove it. Whether a version is stored is now decided by that version's own files: each Maven key is read once into group, artifact, version and file name, and a key of another artifact or a maven-metadata.xml in the version directory no longer counts.
  • A request for a cached npm packument holds far less memory (#1305) — one request for a cached packument held about ten times the document when the client asked for the abbreviated form (Accept: application/vnd.npm.install-v1+json, what pnpm sends), because the whole document was built as a tree in memory and the kept fields were copied out of it: ten parallel pnpm install runs of a package with a 16 MB packument, such as typescript, took NORA past 1.8 GiB. The abbreviated form is now read from the document in one pass, one version at a time, and the request holds at most about two and a half times the document. A request for the full document now holds it once: the local store reads a file into a buffer of its size rather than one grown by doubling, the record NORA keeps at the head of a cached copy is cut off without copying the document, and the tarball links of a copy are checked once per request rather than twice. The bytes a client gets are unchanged, and so are the storage round-trips of a request. The number of requests in flight is still not limited, so the memory still grows with them.

Install

# x86_64
curl -LO https://github.com/getnora-io/nora/releases/download/v1.4.7/nora-linux-amd64
chmod +x nora-linux-amd64
sudo mv nora-linux-amd64 /usr/local/bin/nora

# ARM64 (Apple Silicon, Graviton, Ampere)
curl -LO https://github.com/getnora-io/nora/releases/download/v1.4.7/nora-linux-arm64
chmod +x nora-linux-arm64
sudo mv nora-linux-arm64 /usr/local/bin/nora

Docker

docker pull getnora/nora:1.4.7
Variant Image Platforms
Alpine (default) getnora/nora:1.4.7 amd64, arm64
RED OS getnora/nora:1.4.7-redos amd64
Astra Linux SE getnora/nora:1.4.7-astra amd64
GHCR ghcr.io/getnora-io/nora:1.4.7 amd64, arm64

DEB / RPM

# Debian / Ubuntu / Astra Linux (amd64)
curl -LO https://github.com/getnora-io/nora/releases/download/v1.4.7/nora-amd64.deb
sudo dpkg -i nora-amd64.deb

# RHEL / Fedora / RED OS (amd64)
curl -LO https://github.com/getnora-io/nora/releases/download/v1.4.7/nora-amd64.rpm
sudo rpm -i nora-amd64.rpm

Changelog

See CHANGELOG.md

Don't miss a new nora release

NewReleases is sending notifications on new releases.