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.
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").
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)
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]>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The
@ekklesia/*package registry moved with the repositories tohttps://git.zayin.net/api/packages/Zayin/npm/. The oldgit.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_REGISTRYpoints at the Zayin registry.docs/development/releases.mdanddocs/module-development/README.md: registry URL and owner (Zayin).scripts/test-package-publication.sh: the disposable-Gitea proof's main owner is nowZayin, 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-publicationpasses (11 tests; proof passed); root tests 152 passed;format:checkclean.Before the next publication, the
EKKLESIA_PACKAGES_PUBLISH_TOKENsecret must belong to a publisher account in aZayinpackage-publishers team (docs/development/releases.md, "Publishing the train").🤖 Generated with Claude Code
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.