Rewrite the release pipeline README as a reference The page told the release as a story: the tag grammar was spread over three paragraphs, the bucket and the registries were used before they were named, workflow names changed form from one mention to the next, and the notes a maintainer needs sat as asides inside procedure steps. It was also hard-wrapped at a column. It now defines its terms first, gives the tag kinds and the rules the tag script applies in one place, lists what Build & Deploy publishes where with the exact file and image names, describes each workflow and script with its inputs and outputs, and keeps the release procedure, repository configuration, local dry runs and verification as sections of their own.
__________
Type: commit
Hash: 6ae737c02aeaa9617ecb767c6f0eaf6f9a1ba36b
Created: yesterday
__________
gr0v1ty/nano-node:6ae737c02aeaa9617ecb767c6f0eaf6f9a1ba36b
| Test Case | Status | Duration | Median Deviation | Log | Graph |
|---|---|---|---|---|---|
| No test results available yet. Check the GitHub test run for job status and logs. | |||||