ipympl
ipympl copied to clipboard
NPM Relase action broken
There seem to be two issues:
jupyterlabis 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.
- 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
- I think will require intervention from @tacaswell or someone else with the power mess around with repo secrets
There may be some hints for 2 here: https://sergiodxa.com/articles/github-actions-npm-publish
possible using --access public and maybe specifying the registry
For now I manually publish version 0.11.0
We could probably adopt jupyter-releaser and remove the action
@ianhi Email me so we can coordinate on what secrets need to be where.
Just ran into this again with 0.11.3 https://github.com/matplotlib/ipympl/actions/runs/4187384014/jobs/7257141068
And by coming back here realized that I never followed up... though looking again im not sure that the secrets need to be updated? they're already present
As a follow-up to #416, was this fixed already? :)
Wondering if I still need to match our user-side ipympl versions in kernels when running on HPC-center provided Jupyter instances.