Repository navigation
5.0.0
Breaking Changes
- ArgoCD sync is opt-in on every restart and deploy flow:
k8s restart-msandsynth deployno longer runargocd app syncbefore the ETL. Pass--sync(now available onrestart-schema,restart-etl,restart-ms,dict deployandsynth deploy) to keep the old behaviour (bc5000e) k8s restart-mshonours--restart-services; its fallback order is the documented sheepdog, peregrine, guppy, portal (bc5000e)metadata upload(single study) requires the typed production confirmation, likeupload-allalready did (74f4d43)
Features
metadata upload --release <tag>andupload-all --release: upload a specific release of a study, resolved from the registry path and verified in S3 (DataImportOrder.txt plus node JSONs) before dispatch, on the laptop even for--on ec2(74f4d43)study set --pathverifies the new S3 prefix and gains--dry-run/--no-verify; newconfig study-setalias; the config group help, README andg3dt docsnow point to it (9b60a8e)g3dt --version;g3dt dict statusshows the declared dictionary version next to the one stamped on the deployed S3 object, with--strictexiting 1 on drift (228f68c)
Other
- Help-text polish from a new-developer audit: production gates stated wherever they run, laptop/browser notes and examples on every
k8scommand,--whichexplained onpipeline,jobsgroup help, a glossary ing3dt docs, one name for the CDK template repo, pipx install notes (d2fd70d)
Full Changelog: 4.3.0...5.0.0