fix: point js client package metadata at UiPath/coreipc - #158
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
5 tasks
andreihodoroaga
approved these changes
Sep 15, 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
2 participants
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.
src/Clients/js/package.jsonstill pointsrepository,bugsandhomepageateduard-dumitru/js-multitargeting, a personal repo the JS client no longer lives in. This points all three atUiPath/coreipc.Why it matters beyond tidiness
webpack.common.jsbuilds the published packages by spreading this file —generate-package-json-webpack-plugintakes the basepackage.json, stripsscripts/dependencies/devDependencies, and overridesnameto@uipath/coreipcor@uipath/coreipc-web. So these three fields are what ends up in the published metadata for both packages.That's currently visible on npmjs:
@uipath/coreipc@2.5.1-20260209-02carries thejs-multitargetingURLs and has no attestations.It also blocks provenance. npm verifies
repository.urlagainst the repository the build actually ran in and refuses to publish on a mismatch, so Trusted Publishing cannot work until this lands.Scope
Metadata only — no build, packaging or dependency changes.
authoris deliberately left alone.Split out of #157 so it can be reviewed and merged on its own; #157 depends on it.
🤖 Generated with Claude Code