ci: add frontend UI registry audit workflow#2526
Merged
Merged
Conversation
Audits PRs touching frontend/src against the redpanda-ui registry for outdated/locally-modified components and off-token colour/utility usage, posting a sticky PR comment and failing on findings. Builds the registry manifest (packages/registry/registry.json is a gitignored build artifact) before running the lookout audit-changes CLI, mirroring the proven cloudv2 registry-drift workflow. UX-1330
The job GITHUB_TOKEN is scoped to console only, so checking out the
private redpanda-data/ui-registry repo 404s ('Repository not found').
Fetch the org-wide actions bot token from AWS Secrets Manager and use it
for the checkout, mirroring fork-pr-dispatch.yml and cloudv2's
registry-drift workflow. Adds id-token: write for OIDC.
UX-1330
Contributor
✅ Clean — no registry drift, off-token colours, or ad-hoc classesApp:
Generated by lookout audit-changes. |
c-julin
changed the title
malinskibeniamin
approved these changes
Jun 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds a
Frontend UI AuditGitHub Actions workflow that runs on PRs touchingfrontend/src/**. It audits frontend code against theredpanda-data/ui-registryfor:red-500,indigo-300) instead of semantic tokenstext-[11px],bg-[#0f1626])Findings are posted as a sticky PR comment, and the job fails if any are found (
--fail-on any).Why this shape
Modeled on the proven cloudv2
registry-drift.yml. The key correctness point:audit-changes.tsreadspackages/registry/registry.json, which is a gitignored build artifact — so the workflow runsbun install+bun run registry:buildin the checked-out ui-registry before invoking the audit. Without this step the audit fails withENOENT.Differences from cloudv2 (intentional):
--fail-on any(console blocks PRs) vs cloudv2's informational--fail-on none.UI_REGISTRY_TOKEN/GITHUB_TOKENrather than cloudv2's AWS Secrets Manager bot token (different infra).