chore: publish packages to the registry's current Zayin location #93

Open
ekklesia-bot wants to merge 1 commits from chore/zayin-package-registry into main
Member

The @ekklesia/* package registry moved with the repositories to https://git.zayin.net/api/packages/Zayin/npm/. The old git.riverofglorymn.org/api/packages/River_of_Glory_Church/npm/ address now answers 502, so the next manual Publish packages run would fail. (Signage hit the same 502 at install; it is fixed in Zayin/Signage#18.)

Changes:

  • .github/workflows/publish-packages.yml: EKKLESIA_PACKAGES_REGISTRY points at the Zayin registry.
  • docs/development/releases.md and docs/module-development/README.md: registry URL and owner (Zayin).
  • scripts/test-package-publication.sh: the disposable-Gitea proof's main owner is now Zayin, mirroring production.

Left unchanged on purpose: the org.riverofglorymn.ekklesia.ci.* Docker label keys. They are identifiers the CI sweep matches on, not hosts, and renaming them would orphan stacks labelled by older runs. Historical ADR text is also unchanged.

Verification: pnpm test:package-publication passes (11 tests; proof passed); root tests 152 passed; format:check clean.

Before the next publication, the EKKLESIA_PACKAGES_PUBLISH_TOKEN secret must belong to a publisher account in a Zayin package-publishers team (docs/development/releases.md, "Publishing the train").

🤖 Generated with Claude Code

The `@ekklesia/*` package registry moved with the repositories to `https://git.zayin.net/api/packages/Zayin/npm/`. The old `git.riverofglorymn.org/api/packages/River_of_Glory_Church/npm/` address now answers 502, so the next manual **Publish packages** run would fail. (Signage hit the same 502 at install; it is fixed in Zayin/Signage#18.) Changes: - `.github/workflows/publish-packages.yml`: `EKKLESIA_PACKAGES_REGISTRY` points at the Zayin registry. - `docs/development/releases.md` and `docs/module-development/README.md`: registry URL and owner (`Zayin`). - `scripts/test-package-publication.sh`: the disposable-Gitea proof's main owner is now `Zayin`, mirroring production. Left unchanged on purpose: the `org.riverofglorymn.ekklesia.ci.*` Docker label keys. They are identifiers the CI sweep matches on, not hosts, and renaming them would orphan stacks labelled by older runs. Historical ADR text is also unchanged. Verification: `pnpm test:package-publication` passes (11 tests; proof passed); root tests 152 passed; `format:check` clean. Before the next publication, the `EKKLESIA_PACKAGES_PUBLISH_TOKEN` secret must belong to a publisher account in a `Zayin` package-publishers team (`docs/development/releases.md`, "Publishing the train"). 🤖 Generated with [Claude Code](https://claude.com/claude-code)
ekklesia-bot added 1 commit 2026-10-13 03:24:04 +00:00
chore: publish and document packages at the registry's current Zayin location
CI / verify (pull_request) Successful in 1m17s
CI / infrastructure-smoke (pull_request) Successful in 31s
CI / package-release (pull_request) Successful in 49s
CI / image-build (pull_request) Successful in 59s
CI / migration-smoke (pull_request) Successful in 2m16s
CI / deploy-smoke (same-origin) (pull_request) Successful in 49s
CI / package-publication (pull_request) Successful in 56s
CI / deploy-smoke (split) (pull_request) Successful in 2m39s
2d861c6bf0
The package registry moved with the repositories to
git.zayin.net/api/packages/Zayin/npm/; the old River_of_Glory_Church address
now answers 502, so the next manual Publish packages run would have failed.
Point the workflow, the release and module-development docs, and the
disposable-Gitea publication proof's owner at Zayin. The CI Docker label keys
keep their names: they are identifiers the sweep matches on, not hosts.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
All checks were successful
CI / verify (pull_request) Successful in 1m17s
Required
Details
CI / infrastructure-smoke (pull_request) Successful in 31s
Required
Details
CI / package-release (pull_request) Successful in 49s
Required
Details
CI / image-build (pull_request) Successful in 59s
Required
Details
CI / migration-smoke (pull_request) Successful in 2m16s
Required
Details
CI / deploy-smoke (same-origin) (pull_request) Successful in 49s
Required
Details
CI / package-publication (pull_request) Successful in 56s
Required
Details
CI / deploy-smoke (split) (pull_request) Successful in 2m39s
Required
Details
This pull request doesn't have enough required approvals yet. 0 of 1 official approvals granted.
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin chore/zayin-package-registry:chore/zayin-package-registry
git checkout chore/zayin-package-registry
Sign in to join this conversation.
No Reviewers
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Zayin/Ekklesia#93