MLE-31583 Force public npm repo for publishing - #1123
Merged
Conversation
rjdew-progress
requested review from
RitaChen609,
jonmille,
ngodugu-marklogic and
rjrudin
as code owners
September 9, 2026 00:06
Contributor
There was a problem hiding this comment.
🟡 Changes recommended
The workflow’s repo .npmrc disables lifecycle scripts (ignore-scripts=true), so publishing to npmjs will omit expected publish-time artifacts unless the workflow generates them explicitly before npm publish.
Once you've addressed the issues Copilot identified, you can request another Copilot review.
Pull request overview
This PR updates the release-publish GitHub Actions workflow to ensure npm publish targets the public npm registry (npmjs), rather than the repository’s default registry configured in .npmrc.
Changes:
- Force
npm publishto usehttps://registry.npmjs.org/via an explicit--registryflag.
File summaries
| File | Description |
|---|---|
| .github/workflows/npm-publish-packages.yml | Forces publish step to target the public npm registry during release publishing. |
Review details
- Files reviewed: 1/1 changed files
- Comments generated: 1
- Review effort level: Lite
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Comment on lines
26
to
+27
| # TODO: Create a way to run non-integration tests that don't rely on a MarkLogic Server instance | ||
| - run: npm publish # Or: npm stage publish | ||
| - run: npm publish --registry=https://registry.npmjs.org/ # Or: npm stage publish |
rjrudin
approved these changes
Sep 9, 2026
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
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.
No description provided.