libfn has submissions in flight to four package registries: Conan Center, vcpkg, Bazel Central Registry and nixpkgs. Once accepted, each registry needs a version update after every release — and CONTRIBUTING ## Releasing says nothing about it, so the knowledge currently lives nowhere a contributor would find it.
Add a short subsection after the release-completion criterion listing the registries and the update mechanism for each. It is post-release follow-through by definition — a registry entry references the released artifacts, so it cannot precede the release — and must not be worded as a step of cutting the release.
Write it only after the next release exercises the update path once: the per-registry mechanism (Conan Center bump PR, vcpkg version-database PR, publish-to-bcr app vs. manual BCR module PR, nixpkgs r-ryantm auto-bump review vs. manual) is partly undetermined until proven, and CONTRIBUTING's timeless-present register has no room for speculation.
Assisted-by: Claude:claude-fable-5
libfn has submissions in flight to four package registries: Conan Center, vcpkg, Bazel Central Registry and nixpkgs. Once accepted, each registry needs a version update after every release — and CONTRIBUTING
## Releasingsays nothing about it, so the knowledge currently lives nowhere a contributor would find it.Add a short subsection after the release-completion criterion listing the registries and the update mechanism for each. It is post-release follow-through by definition — a registry entry references the released artifacts, so it cannot precede the release — and must not be worded as a step of cutting the release.
Write it only after the next release exercises the update path once: the per-registry mechanism (Conan Center bump PR, vcpkg version-database PR, publish-to-bcr app vs. manual BCR module PR, nixpkgs r-ryantm auto-bump review vs. manual) is partly undetermined until proven, and CONTRIBUTING's timeless-present register has no room for speculation.
Assisted-by: Claude:claude-fable-5