Skip to content

[Hermes] Restore npm-publish.yml — repo has legitimate npm wrapper#9

Merged
Coding-Dev-Tools merged 1 commit into
mainfrom
hermes/configdrift/restore-npm-publish-workflow
May 18, 2026
Merged

[Hermes] Restore npm-publish.yml — repo has legitimate npm wrapper#9
Coding-Dev-Tools merged 1 commit into
mainfrom
hermes/configdrift/restore-npm-publish-workflow

Conversation

@Coding-Dev-Tools
Copy link
Copy Markdown
Owner

Summary

Restores the npm-publish.yml workflow that was incorrectly removed in PR #8.

Why this change

PR #8 removed npm-publish.yml under the assumption that Python repos should not have npm-publish workflows. However, this repo has a legitimate npm wrapper (package.json + cli.js) that allows users to install via npm install -g configdrift. The npm-publish workflow is needed to publish this wrapper to the npm registry.

The npm wrapper pattern (package.json + cli.js → spawns Python CLI) is an intentional distribution strategy across the DevForge portfolio. Removing the publish workflow breaks the ability to release npm packages.

What changed

  • Restored .github/workflows/npm-publish.yml to its pre-PR-8 state

Validation performed

  • Verified package.json and cli.js exist in the repo
  • Verified cli.js is a functional Node.js wrapper that spawns the Python CLI
  • File content matches the original (commit 743aa39)

Risks/rollback

  • Zero risk — restoring a file that existed 1 commit ago
  • If someone intentionally wanted to remove npm distribution, they would also need to remove package.json and cli.js

Follow-ups

The npm-publish.yml was incorrectly removed in PR #8 based on the assumption
that Python repos should not have npm-publish workflows. However, this repo
has a legitimate npm wrapper (package.json + cli.js) that allows users to
install via 'npm install -g configdrift'. The npm-publish workflow is needed
to publish this wrapper to the npm registry.

Reverts the npm-publish.yml removal from commit 888efcf.
@Coding-Dev-Tools Coding-Dev-Tools merged commit f6bfb02 into main May 18, 2026
3 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.

1 participant