Record readable release naming and adopt paired delivery callers #17
No reviewers
Labels
No labels
app-migration
bug
ci-cd
cluster
Documentation
duplicate
enhancement
gpu
invalid
networking
question
security
Storage
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Homelab/Documentation!17
Loading…
Reference in a new issue
No description provided.
Delete branch "kiyi/readable-release-tags"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Owner decision, 2026-09-27
Every future image, bundle and recovery release uses a readable component/version name, such as
gitchauth-theme-v1. Deployment accepts the exact signed tag. Hashes remain in signed provenance and artifact integrity checks.Changes
Record the durable instance decision and adoption requirements. Pair Documentation image/bundle publishers and deploy reader on proposed v1.24.0, exposing optional named releases with readable defaults. Existing signed releases retain their original names and compatibility. Source-security policy is empty and was checked against the current stable-finding schema; no mitigation is renewed.
Dependencies
Review/merge workflows #64, then publish v1.24.0 before adopting these callers. Platform #76 is the paired private GitchAuth/Core adoption. Older caller pins require a reviewed migration before their next release.
Validation
npm run check,npm run build, paired reusable input/version validation andgit diff --checkpassed. Public diff reviewed for secret values; none added. Hosted named publication/deployment remain unverified.