Point release tooling and dependencies at the current Gitea #3

Merged
weichen merged 2 commits from chore/migrate-gitea-endpoints into main 2026-10-23 14:54:57 +00:00
Owner

Why

Gitea 迁移后权威主机是 gitea.naitangbaobao.cn(Web/API 443、Git over SSH 52222),本仓子模块 URL、governance 允许清单、发布脚本默认值与 AGENTS.md 仍指向旧端点。

Evidence

新端点 ls-remote 与旧端点返回同一 HEAD;其余仓库均已改用新端点。

Impact

依赖 URL、checkout 允许清单、DEV_REPO 默认值与文档通道统一到新端点;git-panel 退役说明保留。

Refs

chore/migrate-gitea-endpoints

## Why Gitea 迁移后权威主机是 gitea.naitangbaobao.cn(Web/API 443、Git over SSH 52222),本仓子模块 URL、governance 允许清单、发布脚本默认值与 AGENTS.md 仍指向旧端点。 ## Evidence 新端点 ls-remote 与旧端点返回同一 HEAD;其余仓库均已改用新端点。 ## Impact 依赖 URL、checkout 允许清单、DEV_REPO 默认值与文档通道统一到新端点;git-panel 退役说明保留。 ## Refs chore/migrate-gitea-endpoints
weichen added 1 commit 2026-10-23 14:20:34 +00:00
Point release tooling and dependencies at the current Gitea
governance / governance (pull_request) Failing after 13s
be1aa68d3d
Why: The Gitea migration moved the authoritative host to
gitea.naitangbaobao.cn (Web/API 443, Git over SSH 52222) but this repo still
declared git-ssh.u1680832.nyat.app:31411 in its submodule URLs, governance
allowlist, release build default and AGENTS.md channel description.

Evidence: git ls-remote over the new endpoint answers with the same HEAD as the
legacy one; every other repository already declares the new endpoint, so the
legacy host in this repo is the last inconsistency in the release path.

Impact: dependency URLs, the governance checkout allowlist, DEV_REPO default and
the documented channels now use the current Gitea. The note about the retired
git-panel endpoint stays, since it records a prohibition rather than a use.

Refs: chore/migrate-gitea-endpoints
weichen added 1 commit 2026-10-23 14:54:24 +00:00
Point release tooling and dependencies at the current Gitea
governance / governance (pull_request) Successful in 21s
9dd4015039
Why: The Gitea migration moved the authoritative host to
gitea.naitangbaobao.cn (Web/API 443, Git over SSH 52222). This repo still
declared git-ssh.u1680832.nyat.app:31411 in its dependency URLs, governance
allowlist, release build default and AGENTS.md channel description, and it
pinned a Development-Manager revision whose SSHBase constant still held the
legacy endpoint, so the shared governance gate rejected the new URLs.

Evidence: git ls-remote over the new endpoint answers with the same HEAD as the
legacy one; the governance gate passes locally and in CI after the pin bump;
every other repository already declares the new endpoint.

Impact: dependency URLs, the governance checkout allowlist, DEV_REPO default,
documented channels and the Development-Manager pin now use the current Gitea.
The note about the retired git-panel endpoint stays: it records a prohibition
rather than a use.

Refs: chore/migrate-gitea-endpoints
weichen force-pushed chore/migrate-gitea-endpoints from 548a6e8eb5 to 9dd4015039 2026-10-23 14:54:24 +00:00 Compare
weichen merged commit a2b9a4455a into main 2026-10-23 14:54:57 +00:00
Sign in to join this conversation.
No Reviewers
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: weichen/Agent-System-Releases#3