MokoConsulting/Template-NPM
Template
1
0
Fork 0
Code Issues 6 Pull Requests Releases Wiki Activity

fix(ci): only publish to npm when source, package, or README changes #32

Closed
jmiller wants to merge 1 commits from fix/npm-publish-change-gate into dev
pull from: fix/npm-publish-change-gate
merge into: :dev
Conversation 1 Commits 1 Files Changed 1
+27

1 Commits

Author SHA1 Message Date
jmiller 7d2fea270b fix(ci): only publish to npm when source, package, or README changes
Universal: Pre-Release / Build Pre-Release (${{ inputs.stability || github.ref_name }}) (push) Successful in 15s
Details
Branch Policy Check / Verify merge target (pull_request) Successful in 2s
Details
Universal: PR Check / Branch Policy (pull_request) Successful in 3s
Details
Universal: PR Check / Secret Scan (pull_request) Successful in 10s
Details
Universal: PR Check / Validate PR (pull_request) Successful in 8s
Details
Universal: Auto-Assign / Assign unassigned issues and PRs (pull_request_target) Successful in 2s
Details
Generic: Project CI / Lint & Validate (pull_request) Successful in 25s
Details
Generic: Project CI / Tests (pull_request) Has been cancelled
Details
Universal: PR Check / Build RC Package (pull_request) Has been cancelled
Details
Universal: PR Check / Report Issues (pull_request) Has been cancelled
Details
Branch Cleanup / Delete merged branch (pull_request) Has been skipped
Details
RC Revert / Rename rc/ back to dev/ (pull_request) Has been skipped
Details 
Add a Detect step (fetch-depth 2) that diffs the push and gates the
Setup/Install/Build/Auto-bump/Publish steps on a real change to
src/**, package.json, package-lock.json, tsconfig.json, or README.md.
Manual dispatch and shallow/first commits always publish. Keeps the
npm README (publish data) current without churning versions on chore
or workflow-sync pushes. Single job (no needs:) so the runner dispatches it.

Authored-by: Moko Consulting
 2026-07-18 11:41:40 -05:00