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

NPM Relase action broken #458

Open
ianhi opened this issue Apr 13, 2022 · 6 comments
Open

NPM Relase action broken #458

ianhi opened this issue Apr 13, 2022 · 6 comments

Comments

@ianhi
Copy link
Collaborator

ianhi commented Apr 13, 2022

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
@ianhi
Copy link
Collaborator Author

ianhi commented Apr 13, 2022

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

@ianhi
Copy link
Collaborator Author

ianhi commented Apr 13, 2022

For now I manually publish version 0.11.0

@martinRenou
Copy link
Member

We could probably adopt jupyter-releaser and remove the action

@tacaswell
Copy link
Member

@ianhi Email me so we can coordinate on what secrets need to be where.

@ianhi
Copy link
Collaborator Author

ianhi commented Feb 15, 2023

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

@ax3l
Copy link

ax3l commented May 24, 2023

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants