docs(clone): align badges with sparkline + switch publish to OIDC#38
Merged
Conversation
ob-aion
force-pushed
the
fix/badges-oidc
branch
2 times, most recently
from
7a00608 to
b44b983
Compare
- README badge block now matches sparkline: npm first, ci second (label=ci), drop the branch-stable badge. - ci.yml stops forwarding NPM_PACKAGE_REGISTRY_TOKEN so the reusable workflow takes the OIDC + provenance path. The Trusted Publisher is configured npm-side. - CLAUDE.md documents the one-off token publish for 1.0.0 and the OIDC switch.
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
1 participant
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.
Summary
Post-publish alignment with the sparkline reference and the now-configured npm Trusted Publisher.
Changes
npmfirst,cisecond (withlabel=ciso it reads "ci passing" not "build passing"), drop thebranch-stablebadge. Order is nownpm → ci → license → stars → coroboros.com.NPM_PACKAGE_REGISTRY_TOKEN. The reusable workflow auto-detects: no token → OIDC Trusted Publisher +npm provenance.1.0.1+publish via OIDC.1.0.0(npm has no pre-publish Trusted Publisher form for a not-yet-existing scoped package) and the OIDC switch.Test plan
pnpm lintcleanpackages/sparkline/README.md1.0.1) publishes via OIDC + provenance (verified on the npm package page provenance section)