22
33The top-site release is an ecosystem snapshot. First release each runtime module
44and make sure its exact release tag is available. In this repository, update all
5- seven submodule pointers to those tags, then run and commit both generated
5+ six submodule pointers to those tags, then run and commit both generated
66inputs:
77
88``` console
@@ -21,6 +21,21 @@ lock headers, verifies `docs/ecosystem.json` against the pinned release-tagged
2121submodules, builds the aggregate docs, and publishes the immutable release
2222directory.
2323
24+ For the shared ** v2.1.0** release, publish packages and their versioned docs in
25+ dependency order: * httk-core* first; then * httk-atomistic* , * httk-store* , and
26+ * httk-workflow* ; then * httk-analyse* and * httk-serve* . Before tagging each
27+ dependent module, refresh its committed inventories from the already published
28+ dependency release docs with ` make docs-inventories ` , and run
29+ ` python -m httk.core.docs check-release --tag v2.1.0 ` and ` make docs-lock-check ` .
30+ Locally built wheels can verify a candidate installation, but do not satisfy
31+ these public-index and published-inventory prerequisites.
32+
33+ Once the six modules are released, pin this site's submodules to their exact
34+ ` v2.1.0 ` tags and regenerate the manifest. Release the aggregate documentation,
35+ the * httk-web.github.io* website, and the refreshed * agent-httk-skill* packages
36+ against that snapshot. The website's package dependency also requires
37+ * httk-serve* 2.1.0 to be available first.
38+
2439If a published release needs a known repair, use the approval-gated repair
2540workflow. It replaces only the explicitly selected release tree and leaves
2641other release snapshots untouched.
0 commit comments