chore: the home registry is The Source, never 'the forge' — sweep the misnomer out of the release rail, workflows, and release notes (Forge is a different product; the stored CI secret keeps its historical name)
This commit is contained in:
parent
c6c6ea6b57
commit
09352c2b37
4 changed files with 55 additions and 51 deletions
|
|
@ -3,7 +3,7 @@ name: CI
|
|||
# Branch pushes only — a release TAG deliberately does not re-run CI: the
|
||||
# tagged commit's CI already ran on its branch push, and the runner is
|
||||
# sequential, so tag-triggered matrix jobs (~22 min) would queue AHEAD of the
|
||||
# tag's publish-forge run and starve every release (observed on 8.10.3 and
|
||||
# tag's publish-source run and starve every release (observed on 8.10.3 and
|
||||
# 9.0.0: the publish sat behind the tag's own redundant CI).
|
||||
on:
|
||||
push:
|
||||
|
|
|
|||
|
|
@ -1,10 +1,12 @@
|
|||
name: Publish (forge)
|
||||
name: Publish (The Source)
|
||||
|
||||
# Datacenter-side forge publish, moved off the laptop: an 87MB tarball PUT
|
||||
# over the laptop's WAN times out; the forge's own runner does it in seconds.
|
||||
# Datacenter-side publish to The Source (source.soulcraft.com — our
|
||||
# self-hosted Forgejo; never call it "the forge", Forge is a different
|
||||
# product), moved off the laptop: an 87MB tarball PUT over the laptop's WAN
|
||||
# times out; The Source's own runner does it in seconds.
|
||||
# scripts/release.sh tags + pushes, then polls this workflow's result (npm
|
||||
# view against the forge registry) before it ever touches the npmjs leg —
|
||||
# see the "delegation contract" in scripts/release.sh's forge-publish step.
|
||||
# view against The Source's registry) before it ever touches the npmjs leg —
|
||||
# see the "delegation contract" in scripts/release.sh's home-publish step.
|
||||
|
||||
on:
|
||||
push:
|
||||
|
|
@ -13,7 +15,7 @@ on:
|
|||
|
||||
jobs:
|
||||
publish:
|
||||
name: Publish to the forge registry
|
||||
name: Publish to The Source registry
|
||||
runs-on: ubuntu-latest
|
||||
steps:
|
||||
- uses: actions/checkout@v4
|
||||
|
|
@ -23,20 +25,21 @@ jobs:
|
|||
cache: npm
|
||||
- run: npm ci
|
||||
- run: npm run build
|
||||
- name: Publish + readback-verify on the forge registry
|
||||
- name: Publish + readback-verify on The Source registry
|
||||
env:
|
||||
# The stored repo-settings secret keeps its historical name.
|
||||
FORGE_NPM_TOKEN: ${{ secrets.FORGE_NPM_TOKEN }}
|
||||
run: |
|
||||
set -eo pipefail
|
||||
|
||||
FORGE_NPM_REG="https://source.soulcraft.com/api/packages/soulcraft/npm/"
|
||||
SOURCE_NPM_REG="https://source.soulcraft.com/api/packages/soulcraft/npm/"
|
||||
VERSION="$(node -p "require('./package.json').version")"
|
||||
echo "Publishing @soulcraft/brainy@${VERSION} to the forge registry..."
|
||||
echo "Publishing @soulcraft/brainy@${VERSION} to The Source registry..."
|
||||
|
||||
TMPRC="$(mktemp)"
|
||||
chmod 600 "$TMPRC"
|
||||
{
|
||||
echo "@soulcraft:registry=${FORGE_NPM_REG}"
|
||||
echo "@soulcraft:registry=${SOURCE_NPM_REG}"
|
||||
echo "//source.soulcraft.com/api/packages/soulcraft/npm/:_authToken=${FORGE_NPM_TOKEN}"
|
||||
} > "$TMPRC"
|
||||
|
||||
|
|
@ -56,12 +59,12 @@ jobs:
|
|||
rm -f "$TMPRC"
|
||||
|
||||
if [ "$LANDED_VERSION" != "$VERSION" ]; then
|
||||
echo "::error::Readback verify FAILED — the forge registry reports version '${LANDED_VERSION:-<none>}', expected '${VERSION}'. This is a genuine publish failure, not a benign duplicate."
|
||||
echo "::error::Readback verify FAILED — The Source registry reports version '${LANDED_VERSION:-<none>}', expected '${VERSION}'. This is a genuine publish failure, not a benign duplicate."
|
||||
exit 1
|
||||
fi
|
||||
|
||||
if [ "$PUBLISH_OK" = true ]; then
|
||||
echo "Published and verified @soulcraft/brainy@${VERSION} on the forge registry."
|
||||
echo "Published and verified @soulcraft/brainy@${VERSION} on The Source registry."
|
||||
else
|
||||
echo "::warning::npm publish reported failure, but readback confirms @soulcraft/brainy@${VERSION} is already live on the forge (a prior run or mirror landed it) — treating this run as successful, since the registry content is correct. Any OTHER failure mode would have failed the readback check above instead."
|
||||
echo "::warning::npm publish reported failure, but readback confirms @soulcraft/brainy@${VERSION} is already live on The Source (a prior run or mirror landed it) — treating this run as successful, since the registry content is correct. Any OTHER failure mode would have failed the readback check above instead."
|
||||
fi
|
||||
Reference in a new issue