Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Discussion about the release process

See original GitHub issue

I was interested in getting a release of the NPM package containing #174, so I figured I’ll look into this a bit.



  1. Do we want to maintain a changelog?

  2. We try to keep the version numbers of all these packages in sync, even when there are no changes. This keeps reasoning about versions simple.

    Currently, the NPM Package is 2.0.0 and 4 months old, while the python package is 1.2.0 and 2-3 months old. What should we do on the next release?

  3. Automatic deployment to PyPI on git tag pushes - is it okay for me to setup that? I have created travis PYPI_PASSWORD environment variables holding a PyPI deployment token for individual PyPI packages managed by the jupyterhub-bot PyPI account. I would like to do the same for this project. I would need to get the PyPI user jupyterhub-bot added as a PyPI package maintainer at to be able to do that.

  4. I learned recently about python -m jupyterlab.browser_check, it may be useful in order to do some minimalistic test of the jupyterlab extension, it was used here: The browser_check is meant to ensure jupyterlab can startup without errors, as I figured out from the scripts docstring:

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:14 (10 by maintainers)

github_iconTop GitHub Comments

manicscommented, May 13, 2020

Should we create a jupyterhub-bot npm user just for Travis deploys?

consideRatiocommented, May 21, 2020

@ryanlovett I released npm package 2.1.0 now. i made it 2.1.0 rather than 2.0.2 since i saw quite a few commits and guessed that was appropriate.

Release guide

  1. installed node/npm
  2. cd jupyterlab-server-proxy
  3. npm login -> npm install -> npm publish
Read more comments on GitHub >

github_iconTop Results From Across the Web

5 Steps to a Successful Release Management Process
Learn the five steps to planning your release management process. ... should meet to assess the release's performance and discuss how the deployment...
Read more >
7 Questions to Plan Your Release Management Process
Prolonging the life of an app doesn't start with a post-launch release management process. It must begin even before the first line of...
Read more >
Ask questions about the release process - LinkedIn
How quickly can a developer release their feature once it's complete? What kind of confidence would he have in the release? Would he...
Read more >
What is Release Management? A Complete Overview
Release management is the process of planning, designing, scheduling, testing, deploying, and controlling a software release. It ensures that ...
Read more >
The Essential Guide to Release Management | Smartsheet
Organizations improve the quality, speed, and efficiency of building or updating software by focusing on release management. This is the process of planning, ......
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Post

No results found

github_iconTop Related Hashnode Post

No results found