fix(ci): use ./ prefix for npm publish paths to prevent GitHub repo resolution#103
Merged
litianningdatadog merged 1 commit intomainfrom Mar 25, 2026
Merged
Conversation
…esolution Without the ./ prefix, npm interprets paths like `npm/foo` as GitHub repository shorthands (org/repo) and attempts to clone them via SSH, causing a permission denied error. Prefixing with ./ ensures npm treats them as local directory paths. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
litianningdatadog
requested review from
Copilot,
jchrostek-dd and
kathiehuang
and removed request for
a team
Contributor
There was a problem hiding this comment.
Pull request overview
Adjusts the npm publish step in the release workflow to ensure npm treats package arguments as local directories (not GitHub repo shorthands), preventing unintended SSH/git resolution during publishing.
Changes:
- Prefix npm package publish paths with
./to force local-path publishing for all three platform packages.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
shreyamalpani
approved these changes
Mar 25, 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.
Summary
npm publish npm/foowas being interpreted as a GitHub repo shorthand (org/repo), causing npm to attempt SSH cloning instead of publishing the local directory./prefix explicitly tells npm these are local pathsTest plan
npm publishsucceeds without SSH git errors