NPM Relase action broken

Open
#458 6 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
github-actions, python
Domain
ci-cd, release

Research direction

Start by reviewing the npm section of the release action and its installation steps, then inspect the npm authentication configuration and repository secrets. Done means the action can find jupyterlab during the npm build and publish without the ENEEDAUTH failure.

Written by the indexing model from the issue text.

Description

There seem to be two issues:

  1. jupyterlab is not installed for the npm section
$ jupyter labextension build --development True .
/bin/sh: 1: jupyter: not found
error Command failed with exit code 127.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
error Command failed with exit code 127.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
error Command failed with exit code 127.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.
  1. Some sort of issue with NPM keys
npm notice 
npm ERR! code ENEEDAUTH
npm ERR! need auth This command requires you to be logged in to https://registry.npmjs.org/
npm ERR! need auth You need to authorize this machine using `npm adduser`

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/runner/.npm/_logs/2022-04-13T18_03_18_823Z-debug-0.log
Error: Process completed with exit code 1.

1 is an easy fix, we just need to pip install jupyterlab

  1. I think will require intervention from @tacaswell or someone else with the power mess around with repo secrets
Dominant language
Jupyter Notebook
Stars
1.7k
Forks
234
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from matplotlib/ipympl

All issues in matplotlib/ipympl

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.