-
Notifications
You must be signed in to change notification settings - Fork 64
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
Previously published versions no longer ignored #563
Comments
When I try to publish an old version of a different package using
This one should be picked up by the check above. I wonder if there is a different message when publishing with provenance, or in a newer NPM version. |
Maybe it is related to a recent transition to node 20.x? I see |
Nope, same error message seen locally with node 20.x and npm 10.5.0. I do not see an easy way forward other than merging #564 and testing it out live on lumino to get the error logs. |
Thank you! It is failing with:
So this looks like configuration issue for lumino rather than what I initially suspected. Is there documentation on how to configure it to work, or do you know how to fix it? |
Ah, I think I accidentally deleted the NPM_TOKEN secret, I just added it back. |
Thanks, this helped! |
The releaser has logic to ignore previously published npm versions on upload:
jupyter_releaser/jupyter_releaser/lib.py
Lines 443 to 451 in ac38c6a
it was used in lumino to only publish packages which had versions bumped, but it is no longer working as of today: jupyterlab/lumino#693
I am not sure if it has something to do with jupyterlab/lumino#690, or if NPM just changed the error message. Unfortunately, the error message is not seen in the traceback (which I think should be fixed too).
To see what the error message is we need something like:
stderr = e.stderr if "EPUBLISHCONFLICT" in stderr or "previously published versions" in stderr: continue else: + util.log(stderr) raise e
The text was updated successfully, but these errors were encountered: