Nightly builds¶
Nightly builds are automated snapshots of the
develop branch,
published so that fixes and new features can be tested before they are released.
These are not releases
A nightly build is unstable, has no version number of its own, and has not been through the release process. It is never published to Maven Central. For analyses you intend to publish, use the latest stable release instead.
Latest nightly¶
The dev-latest tag always points at the most recent nightly, so these links
never go stale:
The version and commit each build came from are recorded in the
dev-latest release notes.
Because the filenames are constant, the nightly can also be fetched from a
script:
curl -LO https://github.com/maize-genetics/tassel/releases/download/dev-latest/tassel-5-standalone-nightly.tar.gz
tar -xzf tassel-5-standalone-nightly.tar.gz
The same release also carries a dated copy of each archive
(tassel-5-standalone-v<version>-dev.<date>.tar.gz), so you can tell which
build you downloaded. The constant-named archive is a copy of that dated one, so
it unpacks into a dated folder such as tassel-5-standalone-v5.2.98-dev.20260801/
— which is the other way to identify a build fetched from the stable URL above.
Running it is otherwise identical to the released standalone distribution — see
the standalone guide.
All nightly builds¶
Every nightly is also archived under its own dated tag, dev-YYYYMMDD. The
newest 14 are kept; older ones are deleted automatically.
Loading nightly builds…
If the list above is unavailable, browse the
GitHub releases
page and look for prereleases tagged dev-.
How they are built¶
The nightly workflow
runs at 05:00 UTC and builds only when develop has new commits since the last
nightly, so there is no build on quiet days. It runs the full test suite first:
a nightly that fails to appear means develop is broken, not that nothing
changed. For the full picture, see
Releasing.