Uh oh!
There was an error while loading. Please reload this page.
Feat/private registry - #362
Conversation
🦋 Changeset detectedLatest commit: dec3baf The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Joozty
commented
May 3, 2024
@Andarist can this be merged please? |
booleans-oss
commented
May 13, 2024
+1 as this is exactly what I need |
brad-mccormick
commented
Jul 24, 2024
I think this is moving in the right direction and thanks @dohaicuong for getting this PR going. I've had the same issue since last year and I'm just now coming back to it. Our packages are stored in a private Artifactory registry which utilizes basic auth (see: Artifactory Basic Auth). That means the .npmrc is expected to have npm has a set of supported fields for authentication which could be mirrored. For example: There's also still some hardcoding of npm registry urls here. Maybe out of scope for this PR, but the reality is you could be publishing to more than one registry, so I'm not sure how useful this is. Lines 76 to 87 in dec3baf |
graffhyrum
commented
Sep 19, 2024
+1 |
dikaso
commented
Nov 13, 2024
Also waiting for this one. How can we help? |
izayl
commented
Feb 28, 2025
any progress about this pr? |
belfz
commented
Oct 17, 2025
any chance this will be merged? |
I've encounter problem when using changesets/action when I'm using the private registry that is not npm.
Upon looking into it the problem seems to coming from the bellow line where it only check for npm registry name.
However, beside npm registry, we also have github registry and custom domain gitlab registry.
Hence I'm making the change here to address for this problem.
Thank you the team for your work on maintaining this tool!