Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

yarn2 workspace monorepo: Can't handle workspace: dependencies. #6092

Closed
1 task done
fjakobs opened this issue Nov 9, 2022 · 2 comments · Fixed by #8099
Closed
1 task done

yarn2 workspace monorepo: Can't handle workspace: dependencies. #6092

fjakobs opened this issue Nov 9, 2022 · 2 comments · Fixed by #8099
Labels
L: javascript:yarn npm packages via yarn T: bug 🐞 Something isn't working

Comments

@fjakobs
Copy link

fjakobs commented Nov 9, 2022

Is there an existing issue for this?

  • I have searched the existing issues

Package ecosystem

yarn

Package manager version

3.2.1

Language version

Node.js 16.x

Manifest location and content before the Dependabot update

No response

dependabot.yml content

version: 2
updates:
  - package-ecosystem: "npm"
    directory: "/packages/databricks-sdk-js"
    schedule:
      interval: "daily"
    ignore:
      - dependency-name: "@databricks/*"          
  - package-ecosystem: "npm"
    directory: "/packages/databricks-vscode"
    schedule:
      interval: "daily"
    ignore:
      - dependency-name: "@databricks/*"    
  - package-ecosystem: "npm"
    directory: "/packages/databricks-vscode-types"
    ignore:
      - dependency-name: "@databricks/*"    
    schedule:
      interval: "daily"

Updated dependency

No response

What you expected to see, versus what you actually saw

I'm using the yarn workspace feature to manage a mono repo with several node.js packages. The different packages define dependencies to each other in the form of workspace: links:

"@databricks/databricks-sdk": "workspace:^",

Dependabot failes to resolve these dependencies and instead tries to look them up on npm, which results in the following error:

 Dependabot can't authenticate to a private package registry
The following private package registry was used and caused the update to fail: registry.npmjs.org.

Screenshot 2022-11-09 at 15 08 22

From the logs:

  proxy | 2022/11/08 17:06:26 [036] GET https://registry.npmjs.org:443/@databricks%2Fdatabricks-sdk
  proxy | 2022/11/08 17:06:26 [036] 404 https://registry.npmjs.org:443/@databricks%2Fdatabricks-sdk
  proxy | 2022/11/08 17:06:26 [038] GET https://www.npmjs.com:443/package/@databricks/databricks-sdk
  proxy | 2022/11/08 17:06:27 [038] 302 https://www.npmjs.com:443/package/@databricks/databricks-sdk
  proxy | 2022/11/08 17:06:27 [040] GET https://www.npmjs.com:443/login?next=%2Fpackage%2F%40databricks%2Fdatabricks-sdk
  proxy | 2022/11/08 17:06:27 [040] 429 https://www.npmjs.com:443/login?next=%2Fpackage%2F%40databricks%2Fdatabricks-sdk
updater | INFO <job_504761053> Handled error whilst updating @databricks/databricks-sdk: private_source_authentication_failure {:source=>"registry.npmjs.org"}

This is not a surprise since the package doesn't exist on NPM.

Native package manager behavior

No response

Images of the diff or a link to the PR, issue, or logs

No response

Smallest manifest that reproduces the issue

No response

@fjakobs fjakobs added the T: bug 🐞 Something isn't working label Nov 9, 2022
@fjakobs
Copy link
Author

fjakobs commented Nov 9, 2022

Creating a new ticket instead of re-opening #3702

@jeffwidman jeffwidman added the L: javascript:yarn npm packages via yarn label Nov 9, 2022
@jeffwidman jeffwidman changed the title yarn2 workspace monorepo: Can't to hndle workspace: dependencies. yarn2 workspace monorepo: Can't handle workspace: dependencies. Feb 6, 2023
@vluoto
Copy link

vluoto commented Aug 9, 2023

For what it's worth, we are experiencing similar issues with pnpm where entries such as

"@organisation/modulemcmoduleface": "workspace:*",

result in

Screenshot 2023-08-09 at 15 55 35

and

updater | Dependabot encountered '1' error(s) during execution, please check the logs for more details.
updater | +--------------------------------------------------------------------------+
updater | |                      Dependencies failed to update                       |
updater | +----------------------------------+---------------------------------------+
updater | | @organisation/modulemcmoduleface | private_source_authentication_failure |
updater | +----------------------------------+---------------------------------------+

in logs.

We also tried ignoring said dependency with

ignore:
  - dependency-name: "@organisation/modulemcmoduleface"

to no avail.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
L: javascript:yarn npm packages via yarn T: bug 🐞 Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants