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
jmiller commented 2026-07-18 16:42:00 +00:00
Owner
Copy Link
Copy Source

npm-publish.yml now gates publishing on a real content change.

Why: the workflow published on every push to main (unless [skip ci]), which caused version churn on chore/workflow-sync pushes and required remembering [skip ci]. It also meant README-only updates were easy to miss on npm.

What: a Detect step (checkout fetch-depth 2) diffs HEAD~1..HEAD; Setup/Install/Build/Auto-bump/Publish run only if src/**, package.json, package-lock.json, tsconfig.json, or README.md changed. workflow_dispatch and shallow/first commits always publish. Single job (no needs:) so it dispatches on the self-hosted runner.

Cascades to child npm repos via workflow-sync on merge to Template-NPM main.

https://claude.ai/code/session_01D4REEaFAKdMPfijyUeBbrh

npm-publish.yml now gates publishing on a real content change. Why: the workflow published on every push to main (unless [skip ci]), which caused version churn on chore/workflow-sync pushes and required remembering [skip ci]. It also meant README-only updates were easy to miss on npm. What: a Detect step (checkout fetch-depth 2) diffs HEAD~1..HEAD; Setup/Install/Build/Auto-bump/Publish run only if src/**, package.json, package-lock.json, tsconfig.json, or README.md changed. workflow_dispatch and shallow/first commits always publish. Single job (no needs:) so it dispatches on the self-hosted runner. Cascades to child npm repos via workflow-sync on merge to Template-NPM main. https://claude.ai/code/session_01D4REEaFAKdMPfijyUeBbrh
jmiller added 1 commit 2026-07-18 16:42:02 +00:00
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
7d2fea270b 
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
jmiller commented 2026-07-18 18:29:11 +00:00
Author
Owner
Copy Link
Copy Source

Closing as superseded by #33 (merged to main via #39).

PR #32 gated npm publishing on a hardcoded ^src/ change filter, which conflicts with the Moko standard (source/, not src/) and duplicates a value that already lives authoritatively in the metadata API (entry_point). #33 reimplements the gate on top of the resolve-source-dir composite action (reads entry_point, cross-checks the Makefile, fail-closed, errors on conflict), so the gate can't drift from the real source dir. The src/ → source/ migration (#34) and two-zip release (#35) also landed. This branch is now on a stale base; no work is lost.

Authored-by: Moko Consulting

Closing as **superseded by #33** (merged to `main` via #39). PR #32 gated npm publishing on a hardcoded `^src/` change filter, which conflicts with the Moko standard (`source/`, not `src/`) and duplicates a value that already lives authoritatively in the metadata API (`entry_point`). #33 reimplements the gate on top of the `resolve-source-dir` composite action (reads `entry_point`, cross-checks the Makefile, fail-closed, errors on conflict), so the gate can't drift from the real source dir. The `src/ → source/` migration (#34) and two-zip release (#35) also landed. This branch is now on a stale base; no work is lost. Authored-by: Moko Consulting
jmiller closed this pull request 2026-07-18 18:29:12 +00:00

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
breaking-change
Breaking API or behavior change
 ci-cd
CI/CD pipeline changes
 config
Configuration changes
 dependencies
Dependency updates
 deploy-failure
Deployment failed
 docker
Docker/container changes
 documentation
Documentation changes
 good first issue
Good for newcomers
 health-check
Repo health check result
 help wanted
Extra attention needed
 javascript
JavaScript code
 mokostandards
Related to MokoStandards framework
 push-failure
Git push operation failed
 security
Security vulnerability or hardening
 size/l
200-500 lines changed
 size/m
50-200 lines changed
 size/s
10-50 lines changed
 size/xl
500+ lines changed
 size/xs
< 10 lines changed
 standards-drift
Deviates from MokoStandards
 standards-update
MokoStandards compliance update
 sync-failure
Sync or mirror failed
 typescript
TypeScript code
 work-in-progress
Draft or incomplete work
bug
Something is not working
 duplicate
This issue or pull request already exists
 enhancement
New feature
 help wanted
Need some help
 invalid
Something is wrong
 question
More information is needed
 wontfix
This won't be fixed
No labels
Priority -
Type -
Milestone
No items
No Milestone
Assignees
Clear assignees
jmiller (Jonathan Miller)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: MokoConsulting/Template-NPM#32
Delete Branch "fix/npm-publish-change-gate"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?