Reproducible Node.js package builds, signed repositories, runtime images, and release provenance.
- Features
- Requirements
- Setup
- Usage
- Development
- Testing
- Troubleshooting
- Security
- Configuration
- Operations
- Support
- Links
- License
The conductor checks stable Node.js 26, npm, and the CentOS Stream 10 base image. It packages official Node.js x64 binaries as signed RPMs.
It builds an RPM and image when Node.js or npm changes. It reuses the RPM when only the base image changes. It skips release work when all checked inputs match the published release.
Use Node.js 26 or later and npm 12 or later. Install Docker, GnuPG, RPM tools, createrepo_c, and Google Chrome on the packaging host.
Run npm ci from the repository root. Provision the signing key and private environment file before a wet conductor run.
Read the local release guide for RPM installation, image use, conductor runs, and configuration. Browse the documentation index for maintained guides. Read the release contract for authoritative release rules. Read the specifications index before changing repository contracts. Read the release notes for user-visible changes.
Follow AGENTS.md when contributing changes.
Run npm test for tests, lint checks, format checks, dependency checks, and Eliware conventions.
Run npm test -- tests/conductor.test.mjs to run one focused test file.
Check network access to nodejs.org when release discovery fails. Check the GnuPG home and key fingerprint when package signing fails.
Refresh the host login and check package write access when GHCR rejects an image push.
Keep signing keys, webhook URLs, and registry credentials outside Git. Keep repository files read-only for the Node.js HTTP application.
Set runtime, signing, and Git values through the environment. Read configuration details for names, defaults, and requirements.
Install the files in systemd/ and enable the daily timer. Run npm run conductor -- --dry-run to check inputs.
Run npm run conductor -- --wet-run to publish a release when inputs changed. Read the operations guide for details.
For help, questions, or to chat with the author and community, visit:


