mirror of
https://github.com/hanzoai/chartjs-plugin-stacked100.git
synced 2026-10-30 18:45:49 +00:00
zeekay
3916bd6286
Both workflows asked for ubuntu-latest, which no runner on this fleet advertises, so neither could be scheduled here. check.yml is replaced rather than moved. Its name promised lint, type-check and test but its steps were `yarn install && yarn dev`, and it never ran the build. The canonical pair states the gate plainly instead: eslint and jest — which is what `dev` resolves to — followed by the vite build that produces the bundle this package exports. build-delopy.yml is dropped. It published the storybook demo to GitHub Pages through configure-pages, upload-pages-artifact and deploy-pages, a hosting plane this fleet does not run. The demo is no longer published anywhere; `yarn build-storybook` still produces storybook-static for anyone who wants it locally.
23 lines
915 B
YAML
23 lines
915 B
YAML
# Canonical CI/CD config for hanzoai/chartjs-plugin-stacked100 — read by the
|
|
# hanzoai/ci reusable (.hanzo/workflows/cicd.yml) and by platform.hanzo.ai.
|
|
#
|
|
# A fork of an upstream Chart.js plugin, consumed as an npm package: no image,
|
|
# so no `images:` and no `deploy:`. One gate, covering what we consume — the
|
|
# linter, the suites, and the bundle the package exports.
|
|
#
|
|
# `dev` is the package's own name for eslint followed by jest; it is spelled
|
|
# out here rather than left to the `prepare` lifecycle hook, which runs the
|
|
# same checks on install and would make the gate an accident of packaging.
|
|
#
|
|
# `--frozen-lockfile` because yarn.lock is committed: without it a resolution
|
|
# that drifted from the lockfile passes here and breaks for whoever installs.
|
|
|
|
test:
|
|
- name: lint-and-test
|
|
run: |
|
|
set -euo pipefail
|
|
yarn install --frozen-lockfile
|
|
yarn dev
|
|
- name: build
|
|
run: yarn build
|