Commit Graph
3 Commits
Author SHA1 Message Date
GROKandClaude Opus 5 10a29ded6a chore: gitignore .npmrc so a registry token can't be committed
ci / build-and-design (push) Failing after 3s
Publishing to the Gitea npm registry needs an _authToken, and the natural
place to put it is a .npmrc in the repo root — which was not ignored. The
committed .npmrc.example invites exactly that mistake.

The pattern matches the exact filename, so .npmrc.example is unaffected.

Nothing was leaked: no .npmrc has ever been committed here. This is
preventative.

Better still, publish with `npm publish --userconfig <path outside the
repo>` and keep the token out of the working tree entirely — that is how
v0.5.0 was published.

Co-Authored-By: Claude Opus 5 <[email protected]>
2026-08-07 15:00:35 -05:00
Jason Stedwell 822d8e41e6 visual upgrade
ci / build-and-design (push) Failing after 13s
2026-07-23 04:23:19 -05:00
GROK b75012525d feat: initial @jason/ui-kit — tokens, preset, components, motion, blocks, Impeccable
ci / build-and-design (push) Failing after 15s
2026-07-16 00:36:53 -05:00