Record Harbor dev readiness and released workflow adoption #41
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
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Homelab/Documentation!41
Loading…
Reference in a new issue
No description provided.
Delete branch "kiyi/harbor-dev-readiness"
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?
Add Harbor’s initial service preparation to the application inventory, with its selected production/dev hosts, merged service foundation and owner-confirmed missing dev storage/database/runtime prerequisites as of 2026-10-13. Record the prepared four-caller adoption in private
Homelab/the-gitchistry PR #5, keeping hosted application checks, signed bundle publication and live deployment pending. Registry migration remains deferred.Update the security tool image delivery/decision record to show published workflows v1.34.0, while caller adoption and application operation acceptance remain open in workflows #86. Detailed operator steps stay in the owning private repository.
Validation:
npm run check,npm run build,git diff --checkand the installed native Gitleaks 8.30.1 staged hook passed. Reviewed the three-page public diff for secret values and kept private sources as plain-text references. No application deployment or registry cutover is claimed.Reviewed the three changed documentation pages at
e3f37e910a. The Harbor inventory distinguishes the merged service foundation and prepared four-caller workflow update from missing dev runtime prerequisites, signed bundle publication, deployment and registry cutover. I checked the referenced the-gitchistry PR #5 at 67b0ece13ed06f2f9547cb9c35aadec977d90ac3 and its four current caller files: v1.34.0 uses/library_ref and the accepted security-image digest align. Workflows #87 is merged; the public operating record keeps downstream adoption/acceptance pending. All three Documentation source-security/site-check contexts and their exact-head Actions jobs succeeded; there are no prior reviews on this PR. Approval is for this documentation head only, not Harbor PR #5, a runtime acceptance, deployment or merge. Forgejo's changed-file API omitted patch hunks, so I inspected the complete changed-page source instead; I did not rerun local npm checks.