-
-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Issues when releasing 4.0.0b2
#14431
Comments
I just sent a message to the |
For reference everything seems fine at the moment according to https://status.npmjs.org: |
Ah the status is now showing "Degraded performance of npm publish": https://status.npmjs.org/incidents/nhmby0vny5xy |
Looks like it's been resolved: The GitHub Release has now been undrafted: https://github.com/jupyterlab/jupyterlab/releases/tag/v4.0.0b2 |
Leaving the issue open for now to double check the bot token is correct, so it's not an issue for future releases. |
Closing the issue, as the discussion about the token is now happening in jupyterlab/frontends-team-compass#190. |
Tracking issues that happened during the
4.0.0b2
release.HTTP Error 401: Unauthorized
Trying to use the workflows from the repo directly kept giving 401 errors:
HTTP Error 401: Unauthorized
:Commented here: #14176 (comment)
This could be related to the bot
ADMIN_GITHUB_TOKEN
.Packages not available on npm yet
This looks like an issue on npm which might be fixed automatically after a while. It is still
4.0.0-beta.1
for now although the publish step seems to have gone though: https://www.npmjs.com/package/@jupyterlab/application?activeTab=versionsFor reference the release workflow was done from the releaser fork because of the issue mentioned above: https://github.com/jtpio/jupyter_releaser/actions/runs/4794491472/jobs/8527930831
Not sure there is much we can do for now. Will open a ticket on npm if the issue persists.
Once the npm issue is fixed I will undraft the release manually:
The text was updated successfully, but these errors were encountered: