We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Just logging an issue when trying to publish this new version of the package with the releaser: https://github.com/jupyterlab-contrib/jupyterlab-open-url-parameter/releases/tag/v0.2.0
Running the workflows without configuring the repo secrets initially gave issues when trying to publish to npm: https://github.com/jupyterlab-contrib/jupyterlab-open-url-parameter/actions/runs/7526313542
However the secrets seem to be correctly defined at the org level:
To be able to finalize the release, I had to provide my own npm token and add it to the repo:
Noting that the package is correctly added on npmjs.com:
npmjs.com
cc @fcollonval who may know if the NPM_TOKEN in the organization secrets may need a refresh?
NPM_TOKEN
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Just logging an issue when trying to publish this new version of the package with the releaser: https://github.com/jupyterlab-contrib/jupyterlab-open-url-parameter/releases/tag/v0.2.0
Running the workflows without configuring the repo secrets initially gave issues when trying to publish to npm: https://github.com/jupyterlab-contrib/jupyterlab-open-url-parameter/actions/runs/7526313542
However the secrets seem to be correctly defined at the org level:
To be able to finalize the release, I had to provide my own npm token and add it to the repo:
Noting that the package is correctly added on
npmjs.com:cc @fcollonval who may know if the
NPM_TOKENin the organization secrets may need a refresh?The text was updated successfully, but these errors were encountered: