ci(selfhost): stop publishing the legacy gittensory-selfhost image tag

[JSONbored]

Summary

The self-host container image release workflow published every orb-v tag under both the
renamed loopover-selfhost name and the pre-rename gittensory-selfhost name as a
dual-publish alias. This stops publishing under the old name going forward -- only
loopover-selfhost ships from here on.

Already-published tags and digests under the old name are untouched; GHCR has no
server-side alias, so an existing exact-version or digest pin keeps resolving forever
regardless. Only a :latest-style pin stops advancing, which is the accepted tradeoff of
retiring the dual-publish, not something this change works around.

Updates the release workflow's image metadata step and release-notes template, trims the
now-stale dual-publish/alias commentary from the deploy script, release-automation scripts,
and .env.example, and brings the self-hosting docs and unit tests in line with the new
single-name publish.

Scope

• The PR title follows type(scope): short summary Conventional Commit format, for example fix(api): restore profile access checks.
• This PR is focused and does not mix unrelated backend, UI, MCP, docs, dependency, and deploy changes.
• This follows CONTRIBUTING.md and does not reintroduce GitHub Pages, VitePress, site/, or CNAME.
• I linked a currently open issue this PR resolves (e.g. Closes #123) — a linked open issue is required for every contributor PR.

Not a Closes reference: this is one of several PRs landing for #4777 ("Retire every
deprecation shim"), which tracks retiring multiple independent deprecation shims across the
codebase. This PR only retires the self-host container image's dual-publish alias, so it is
Part of #4777 — only the maintainer closes the umbrella issue once every sub-PR has merged.

Validation

• git diff --check
• npm run actionlint (via npm run test:ci)
• npm run typecheck (via npm run test:ci)
• npm run test:coverage locally; codecov/patch requires ≥99% coverage of the lines AND branches you changed (aim for 100% on your diff so CI variance does not fail near the threshold). Global coverage is a non-blocking trend with a loose 90% backstop, not the gate.
• npm run test:workers (via npm run test:ci)
• npm run build:mcp (via npm run test:ci)
• npm run test:mcp-pack (via npm run test:ci)
• npm run ui:openapi:check (via npm run test:ci)
• npm run ui:lint (via npm run test:ci)
• npm run ui:typecheck (via npm run test:ci)
• npm run ui:build (via npm run test:ci)
• npm audit --audit-level=moderate
• New or changed behavior has unit/integration tests for new branches, fallback paths, and sanitizer boundaries

Ran the full npm run test:ci gate locally (all steps, including test:coverage) plus
npm audit --audit-level=moderate — both clean. Also re-ran the three directly affected
unit test files in isolation: test/unit/release-selfhost-notes.test.ts,
test/unit/selfhost-image-deploy.test.ts, test/unit/selfhost-sentry-release.test.ts.

Safety

• No secrets, wallet details, hotkeys, coldkeys, user PATs, private keys, raw trust scores, private rankings, or private maintainer evidence are exposed.
• Public GitHub text stays sanitized, low-noise, and does not imply compensation guarantees or optimization tactics.
• Auth, cookie, CORS, GitHub App, Cloudflare, or session changes include negative-path tests.
• API/OpenAPI/MCP behavior is updated and tested where needed.
• UI changes use live API data or real empty/error/loading states, not production mock/demo fallbacks.
• Visible UI changes include a UI Evidence section below with JPG/JPEG or PNG screenshots arranged as organized, captioned, clickable thumbnails. SVG screenshots are not used as review evidence. Review-only screenshots or recordings are not committed to the repository.
• Public docs/changelogs are updated where needed; changelogs are only edited for release-prep PRs.

No UI Evidence: the only apps/gittensory-ui changes are wording edits to existing
self-hosting docs prose (dropping "deprecated alias" phrasing in favor of "no longer
published to"), not new visual states or layout changes.

Notes

• Part of Retire every deprecation shim #4777.

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	loopover-ui	f768cc5	Commit Preview URL Branch Preview URL	Jul 13 2026, 08:34 PM

[superagent-security]

Superagent didn't find any vulnerabilities or security issues in this PR.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.03%. Comparing base (313342d) to head (f768cc5).
⚠️ Report is 1 commits behind head on main.
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #5650   +/-   ##
=======================================
  Coverage   95.03%   95.03%           
=======================================
  Files         577      577           
  Lines       45920    45920           
  Branches    14695    14695           
=======================================
  Hits        43640    43640           
  Misses       1528     1528           
  Partials      752      752           

Flag	Coverage Δ
shard-1	43.91% <ø> (ø)
shard-2	35.67% <ø> (ø)
shard-3	32.19% <ø> (ø)
shard-4	32.57% <ø> (ø)
shard-5	31.77% <ø> (ø)
shard-6	44.46% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[loopover-orb]

Warning

🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨🟨

⏸️ LoopOver review result - manual review recommended

_{Review updated: 2026-07-13 20:39:13 UTC}

14 files · 1 AI reviewer · 2 blockers · readiness 93/100 · CI green · clean

⏸️ Suggested Action - Manual Review

Review summary
This is a coherent, narrow removal of the dual-publish alias for the self-host container image: the release workflow drops the second `images:` line for `gittensory-selfhost`, and every docs page, script comment, `.env.example`, and unit test that referenced the deprecation-window alias is updated consistently to reflect the new single-name publish. The test updates (`selfhost-sentry-release.test.ts`, `release-selfhost-notes.test.ts`, `selfhost-image-deploy.test.ts`) correctly flip assertions from `toContain` the old alias to `not.toContain` it, matching the workflow's actual new behavior, and the explicit-pin-passthrough test in `selfhost-image-deploy.test.ts` still correctly guards that an operator's explicit legacy reference isn't rewritten by the script (unrelated to the workflow's publish-time change). The one gap is that this PR is 'Part of #4777' rather than closing a dedicated eligible issue, which the repo's contribution checklist itself flags as unresolved.

Nits — 4 non-blocking

• The PR doesn't close a dedicated open issue — it's explicitly 'Part of Retire every deprecation shim #4777', an umbrella tracking issue, and the PR's own checklist leaves the 'linked open issue' box unchecked; confirm this satisfies the maintainer's issue-linkage bar before merge.
• The failing 'Workers Builds: loopover-ui' check isn't explained by anything in this diff (no UI logic changes, only docs text/code samples), so it's likely a pre-existing or infra-level failure rather than something this PR caused — worth a quick check that it's unrelated.
• Since GHCR has no server-side alias and old tags/digest pins will silently stop advancing once `:latest`-style pins are used, consider a one-time deprecation notice in the actual GitHub Release notes (not just docs) for the last dual-published version, so self-hosters watching releases don't miss the cutover.
• Double check `apps/gittensory-ui/src/routes/docs.self-hosting-release-checklist.tsx` and `docs.self-hosting-operations.tsx` for any other stale `gittensory-selfhost` references outside the hunks shown, since both files are large and only partial diffs are visible here.

Concerns raised — review before merging

• No linked issue detected — If this PR is intended to solve an issue, link it explicitly in the PR body.
• Maintainer requires a linked issue — Link the relevant issue (for example Closes #123) before opening the PR.

📋 Copy for AI agents — paste into your coding agent

Fix the following blocker(s) from this PR review:

1. No linked issue detected — If this PR is intended to solve an issue, link it explicitly in the PR body.

2. Maintainer requires a linked issue — Link the relevant issue (for example `Closes #123`) before opening the PR.

Signal	Result	Evidence
Code review	❌ 2 blockers	1 reviewer
Linked issue	⚠️ Missing	No linked issue or no-issue rationale found.
Related work	✅ No active overlap found	No same-issue or scoped active PR overlap found.
Change scope	✅ 20/20	Low review scope from cached public metadata (no linked issue context).
Validation posture	✅ 25/25	PR body includes validation/test evidence.
Contributor workload	✅ 10/10	Author activity: 44 registered-repo PR(s), 36 merged, 320 issue(s).
Contributor context	✅ Confirmed Gittensor contributor	JSONbored; Gittensor profile; 44 PR(s), 320 issue(s).
Gate result	❌ Blocking	Repo-configured hard blocker found.
Improvement	✅ Minor	risk: clean · value: minor — Code changes are accompanied by test evidence.

Review context

• Author: JSONbored
• Role context: owner (maintainer lane)
• Public audience mode: oss maintainer
• Lane context: Repository is configured for direct PR review.
• Public profile languages: not available
• Official Gittensor activity: 44 PR(s), 320 issue(s).
• PR-specific overlap: none found.

Contributor next steps

• Treat this as maintainer-lane context rather than normal contributor-lane activity.
• Explain no-issue PR.
• Link the issue being solved, or explicitly explain why this is a no-issue PR.

Signal definitions

• Related work = same linked issue, overlapping active PRs, or title/path similarity.
• Change scope = cached public metadata such as size labels, draft state, and review-burden hints.
• Validation posture = whether the PR provides enough public validation/test evidence for maintainer review.
• Contributor workload = public contributor activity and cleanup pressure, not a repo-wide quality failure.
• Contributor context = public GitHub/Gittensor identity context; non-Gittensor status is not a blocker.

[BETA] Chat with Gittensory

Ask Gittensory a question about this PR directly in a comment — grounded only in the same cached, public-safe facts shown above, never a new claim.

• @gittensory ask <question> answers contribution-quality Q&A with source citations and freshness.
• @gittensory chat <question> answers in natural prose from cached decision-pack facts via local inference (maintainer/collaborator; read-only).
• A plain-language @gittensory mention with a real question is routed to the closest matching read-only command automatically -- no exact syntax required.

Full command reference: https://gittensory.aethereal.dev/docs/gittensory-commands

Visual preview

Route	Viewport	Before (production)	After (this PR's preview)	Diff
/docs/self-hosting-operations	desktop			—
/docs/self-hosting-operations	mobile			—
/docs/self-hosting-quickstart	desktop			—
/docs/self-hosting-quickstart	mobile			—

Click any thumbnail to open the full-size screenshot. Before = production · After = this PR's preview deploy.

_{🟩 Safe / merged · 🟦 Advisory · 🟨 Held for review · 🟥 Blocked / closed}

---

💰 Earn for open-source contributions like this. Gittensor lets GitHub contributors earn for the work they already do — register to start earning →.

Checked by LoopOver, a quiet PR intelligence layer for OSS maintainers.

• Re-run LoopOver review