* ui: publish @ggml-org/llama-ui from CI when its version moves
ui/lib/ui reaches npm only when someone remembers to publish it by hand, which let 0.3.0
sit a day behind master. The version in its package.json becomes the release: a commit
landing on master with a version npm does not have gets built, linted and published with a
provenance attestation, through OIDC rather than a stored token, as release-publish.yml
already does for GitHub releases. A library change carrying no bump publishes nothing and
says so, on the PR and on the run.
Assisted-by: Llama Chat (unsloth/Qwen-3.8-Flash-Next:IQ4_XS)
* ui: bump @ggml-org/llama-ui to 0.4.0
The library on npm, published before the design system PR merged, holds no entry points for
the Model UI, the app components or the shared constants and enums, and no dependency on
@ggml-org/llama-brand, whose colours the primitives now build on. Consumers import the new
subpaths and get ERR_PACKAGE_PATH_NOT_EXPORTED.
Assisted-by: Llama Chat (unsloth/Qwen-3.8-Flash-Next:IQ4_XS)
* ui: name no environment for the Llama UI publish job
Creating a repository environment needs admin rights the UI maintainers do not hold, so a job
that names one cannot be set up by them. The job works without it: npm's trusted publisher
matches on the repository and the workflow file, and its environment field stays blank to
match. Nothing else in the job depends on an environment.
Assisted-by: Llama Chat (unsloth/Qwen-3.8-Flash-Next:IQ4_XS)
* ui: address review on the Llama UI publish job
- the advisory version check leaves ui.yml for the publish workflow, on a pull_request trigger
whose path filter keeps it off PRs that touch only Llama Chat: a chat-only PR was told to
bump a library it did not change
- publish and verify run on master only. The trusted publisher matches on the repository and
the workflow file, not the branch, so a dispatch from a PR branch - anything with write
access can start one - could publish code no one reviewed. With no environment, this was the
only branch protection in place.
- the registry read after a publish retries six times rather than sleeping once, so a release
the registry is slow to serve is not reported as a failure
- a build metadata suffix (1.2.3+build) is not a prerelease, and versions order by semver's
prerelease rules, so 0.4.0-beta.1 behind a released 0.4.0 is refused instead of shipped to next
- the summary step passes its values through env like the others, actions: read is gone, and the
concurrency comment claims only what the setting does
- npm older than 11.5.1 is refused up front, as it cannot publish with an OIDC token
Assisted-by: Llama Chat (unsloth/Qwen-3.8-Flash-Next:IQ4_XS)
* ui: note the two trusted-publishing traps in the Llama UI README
A publisher names a workflow file that must already be in .github/workflows, so it is added
after this workflow lands rather than before, and one created now publishes only through
staged publishing until npm publish is permitted for it. Provenance comes free with either,
and only on a GitHub-hosted runner.
Assisted-by: Llama Chat (unsloth/Qwen-3.8-Flash-Next:IQ4_XS)
* Update .github/workflows/ui-lib-publish.yml
Co-authored-by: Sigbjørn Skjæret <sigbjorn.skjaeret@huggingface.co>
---------
Co-authored-by: Sigbjørn Skjæret <sigbjorn.skjaeret@huggingface.co>