Skip to content

ci: publish through npm trusted publishing - #9

Closed
iscekic wants to merge 1 commit into
mainfrom
ci/trusted-publishing
Closed

iscekic wants to merge 1 commit into
mainfrom
ci/trusted-publishing

Conversation

@iscekic

@iscekic iscekic commented Nov 13, 2026

Copy link
Copy Markdown
Collaborator

Switches the release job from a stored npm token to npm trusted publishing: the job's OIDC token is exchanged for a short-lived publish credential, and npm attaches the provenance attestation. Node 24 supplies an npm new enough for it. The job now packs the tarball and keeps it as an artifact; a manual run with publish off only packs, so the first version can be published by hand from the exact CI-built tarball before the trusted publisher exists.

@iscekic

iscekic commented Nov 13, 2026

Copy link
Copy Markdown
Collaborator Author

bot: Closing: the package moves into the Kilo-Org/cloud monorepo, so it is no longer published to npm.

@iscekic iscekic closed this Nov 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant