Project operations
Release process
tt is in early development. Only Nightly builds from main are published, and every npm installation uses the next channel.
Stages
How a Nightly is published
NightlyCurrent main
The scheduled main CI publishes the latest development build to npm next automatically.
1.0.0-dev.YYYYMMDD.NImmutable build
A successful scheduled or manually dispatched main CI run produces one versioned artifact set.
npm nextNightly channel
The verified artifacts are published to npm next and attached to a GitHub pre-release.
Operating flow
Prepare, verify, publish
Where does release work land?
All development lands in main through reviewed pull requests. Current public builds are Nightlies produced from that line.
git switch main
git pull --ff-only origin mainHow is a Nightly built?
Scheduled or manually dispatched main CI creates one immutable artifact set. The source version is converted to a unique development version for that run.
# source: 1.0.0
# artifact: 1.0.0-dev.YYYYMMDD.NHow is a Nightly published?
Publish Release reuses the successful CI artifacts, publishes every npm package with next, and creates a GitHub pre-release with the matching immutable version.
npm install --save-dev @openload28/tt-lang@next @openload28/unplugin-tt@next