What — SMonitor 0.16.0 recovery removed the Conda workflow's release trigger. Publishing a future routine GitHub Release such as 0.17.0 would not start any Conda build or upload.
How — Restore the automatic direct-release route only when a pre-tag release decision allows it and the version has no staged or public files. Keep exact-file promotion for staged candidates; fail closed on ambiguous registry state and never overwrite a coordinate.
Why — The 0.16.0 coordinate collision required promotion, not permanent removal of automatic Conda publication for releases that do not need staging. The current workflow silently changes maintainers' expected release procedure.
Record — devguide/pending_bugs/routine_release_no_longer_publishes_conda.md
Shared policy review — uibcdf/molsyssuite#27.
What — SMonitor 0.16.0 recovery removed the Conda workflow's
releasetrigger. Publishing a future routine GitHub Release such as 0.17.0 would not start any Conda build or upload.How — Restore the automatic direct-release route only when a pre-tag release decision allows it and the version has no staged or public files. Keep exact-file promotion for staged candidates; fail closed on ambiguous registry state and never overwrite a coordinate.
Why — The 0.16.0 coordinate collision required promotion, not permanent removal of automatic Conda publication for releases that do not need staging. The current workflow silently changes maintainers' expected release procedure.
Record —
devguide/pending_bugs/routine_release_no_longer_publishes_conda.mdShared policy review — uibcdf/molsyssuite#27.