circagraph
Sign inSign up

openchronology/timeline-app on GitHub

The OpenChronology repository on GitHub, mirrored by och-import-github: issues and pull requests as durations (ongoing while open), what happened to them as moments, plus releases, milestones, commits and branches. The Branches view shows the most recently active branches each in a track of its own.

Source: https://github.com/openchronology/timeline-app

3,131 moments · 2026-10-05 CE 20:21:49 UTC – 2026-11-16 CE 12:10:45 UTC · by @athan · @athan

The package builds take a cached Node.js tarball instead of downloading it in Docker

  • github
  • github/openchronology/timeline-app
  • commit
  • main
  • github/athanclark

Downloading Node.js from nodejs.org inside the .deb and .rpm Docker builds stalls intermittently from GitHub's runners (#367). CI now reads the version from the Debian Dockerfile (scripts/node-tarball.mjs), restores the tarball with actions/cache keyed on that version and architecture, downloads and checks it against SHASUMS256.txt and the pinned SHA-256 on a miss, and gives it to scripts/server-package.mjs in OCH_NODE_TARBALL. The Dockerfiles take it from a node-tarball build context (an empty stage by default, so local builds download as before) and check the pinned SHA-256 either way. Fixes #369 Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_011fFY8eruEi1xAkkMBni13B https://github.com/openchronology/timeline-app/commit/12d12bf25cde742102e46e111a14238b7a62e7c6

Related

Open The package builds take a cached Node.js tarball instead of downloading it in Docker in the timeline

The package builds take a cached Node.js tarball instead…