Release checklist
Use this checklist before registering a release.
1. Package tests
julia --project=. -e 'using Pkg; Pkg.instantiate(); Pkg.test()'2. External correctness
Run both fitting campaigns against R rvinecopulib:
PARITY_N=800 PARITY_FIT_MODE=common \
bash benchmarks/correctness/run_correctness_gate.sh
PARITY_N=800 PARITY_FIT_MODE=default \
bash benchmarks/correctness/run_correctness_gate.shDo not relax tolerances or remove a candidate family to turn a failing gate into a pass. Diagnose the failing family, structure, or numerical primitive instead.
3. Performance snapshot
Refresh the evaluation benchmark and at least one fitting benchmark:
bash benchmarks/run_main.sh
MODE=common N=1000 P=5 REPEATS=3 bash benchmarks/fitting/run_fit.shRun the default fitting benchmark after its correctness gate is green. Record the comparison environment with:
bash benchmarks/correctness/record_environment.sh4. Documentation
Build the documentation from the package root:
julia --project=docs -e '
using Pkg
Pkg.develop(PackageSpec(path=pwd()))
Pkg.instantiate()
include("docs/make.jl")
'Check that the six main documentation sections render correctly and that the version selector exposes dev, stable, and tagged releases after deployment.
5. Release metadata
Before tagging:
set the intended version in
Project.tomlandCITATION.cff;replace
UnreleasedinCHANGELOG.mdwith the release date;add
date-releasedtoCITATION.cff;confirm CI and documentation jobs are green;
register the release only from the tested commit.