26 lines
1.4 KiB
Markdown
26 lines
1.4 KiB
Markdown
# Confirmed rename prerelease publication records
|
|
|
|
These exact originals record Gitea release 6, tag
|
|
`v0.2.0-preview.rename.20260912`, source
|
|
`cbc49a7802fb1bba0dd284fd904c700a0703ae70` and evidence checkpoint
|
|
`506a349b32f3f869ac027d8763c501b61cf79769`.
|
|
|
|
`publish-first/result.json` confirms public prerelease visibility and all three
|
|
downloaded assets at 2026-09-13T00:47:52.474878Z; the terminal action finished at
|
|
00:47:52.873060Z. `create-first` and `upload-first` preserve earlier draft/upload
|
|
steps. API `published_at` reflects draft creation and is separately labeled.
|
|
Exact asset IDs, byte counts and hashes are in the final result and
|
|
[published report](../../release-source-alias-rename-published-20260912.md).
|
|
|
|
The helper and bindings are historical executed evidence. Do not rerun the
|
|
publisher from this relocated directory. Acceptance receipts referenced by
|
|
absolute original paths live in the separately published package/runtime/native
|
|
archives. `sourceBranchHead` is the branch tip checked during publication, not a
|
|
promise that the evidence branch will never advance afterward.
|
|
|
|
The initial static review identified Git tag-helper configuration hazards; the
|
|
parent used purpose-built Gitea MCP tag creation instead. The subsequent review
|
|
proves the API helper changed only its missing-tag message. Historical readiness
|
|
review pending wording precedes the final reviewed documents and bound receipts;
|
|
it does not negate the later successful executed results.
|