docs(release): record the final commit hash in the demo-release summary
This commit is contained in:
@@ -8,9 +8,10 @@
|
||||
to `main`; no rebase/reset/squash/force-push; full git history preserved, as required)
|
||||
- **Start commit** (functional-completion baseline, already accepted):
|
||||
`e0c7ed60112510687627d20a957af91c8b9db7f8`
|
||||
- **Final commit**: see `git log -1` on this branch — this file's own commit necessarily
|
||||
cannot self-reference its own hash; the immediately following commit records it
|
||||
explicitly for a stable, unambiguous reference.
|
||||
- **Final commit**: `294a8176d196e42408c4e99c29ab142771fcec04` (the commit that added this
|
||||
file; a small follow-up commit records this hash explicitly, since a commit cannot
|
||||
self-reference its own hash — `git log -1` on this branch is the authoritative source
|
||||
if it has moved further since).
|
||||
- **Live URL**: `http://192.168.10.150:1236`
|
||||
|
||||
## Demo organisation and context
|
||||
|
||||
Reference in New Issue
Block a user