mirror of
https://github.com/hanzoai/persona.git
synced 2026-10-30 18:24:59 +00:00
zeekay
6f5a8be9d5
publish.yml asked for ubuntu-latest, which no runner in this fleet advertises: that job queued to the timeout rather than failing, so a tag looked published when nothing had run. `node scripts/validate.js` was in package.json and called by nothing; it is now the gate. `binaries:` keeps what the tag was for — `npm pack` builds the same tarball `npm publish` would have uploaded, and the release carries it, so a consumer can install an exact tag. Lost with the old lane: publication to registry.npmjs.org. The forge holds no npm credential, and a lane that cannot authenticate is worse than none.
21 lines
727 B
YAML
21 lines
727 B
YAML
# Canonical CI/CD config for hanzoai/persona — read by the hanzoai/ci reusable
|
|
# (.hanzo/workflows/cicd.yml) and by platform.hanzo.ai.
|
|
#
|
|
# No `images:`: persona is a schema package, not a service.
|
|
#
|
|
# `binaries:` carries what the retired npm lane carried — an artifact that
|
|
# exists at the tag. `npm pack` produces the same tarball `npm publish` would
|
|
# have uploaded, and the reusable attaches it to the forge release, so a
|
|
# consumer can install the exact tag. It does not reach registry.npmjs.org;
|
|
# that needs a publish credential the forge does not hold.
|
|
test:
|
|
- name: validate schemas
|
|
run: |
|
|
set -euo pipefail
|
|
node scripts/validate.js
|
|
|
|
binaries:
|
|
- name: persona
|
|
run: npm pack
|
|
out: "*.tgz"
|