Skip to content

chore: add private:true to prevent npm publish (#4384) - #245

Merged
gibaros merged 2 commits into
mainfrom
chore/fix-npm-publish-config
Mar 23, 2026
Merged

gibaros merged 2 commits into
mainfrom
chore/fix-npm-publish-config

Conversation

@gibaros

@gibaros gibaros commented Mar 17, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Adds "private": true to package.json to prevent this service from being published to npmjs.com
  • This service should only publish Docker images to hub.docker.com/u/mojaloop
  • The CircleCI orb's check_npm_private gate will now skip the publish_npm job

Context

The mojaloop/build CircleCI orb always includes both publish_npm and publish_docker jobs. The publish_npm job gates itself by checking if package.json has "private": true. Without this flag, services with Dockerfiles were incorrectly publishing to both npm and Docker Hub.

Refs: mojaloop/project#4384

Test plan

  • Verify jq '.private' package.json returns true
  • On next release tag, confirm CircleCI publish_npm job logs "Package is private, skipping job"
  • Confirm Docker publish still works normally

🤖 Generated with Claude Code

This service should only publish Docker images to hub.docker.com,
not npm packages to npmjs.com. Adding "private": true causes the
CircleCI orb's check_npm_private gate to skip the publish_npm job.

Refs: mojaloop/project#4384

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@gibaros
gibaros merged commit a039263 into main Mar 23, 2026
15 checks passed
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.

2 participants