Add changelog for 0.10.0

[consideRatio]

@sean-morris @yuvipanda @manics what do you think about cutting 1.0.0? I think we should have 1.0.0 releases of a lot of our old projects instead of sticking around with 0.x.y out of habit.

Questions

• Is it time to cut a release?
• Is it time to cut a 1.0.0 release?
• Is the changelog okay as it is, or do we add something to it?
  Please feel free to push a description or similar to it. I didn't feel well equipped to summarize the changes in this repo since 0.9.0.

[manics]

1.0.0 sounds like a good time to switch master to main? jupyterhub/team-compass#412

[yuvipanda]

I think we should get #177 for 1.0. My gut feel is that it's somewhat involved - the terminal in nbgitpuller is pulled in via hacks on where xterm.js is served from in classic notebook. So let's get a 0.10 out (at least I want one - we have a workshop coming in soon) and then do 1.0 after that?

[consideRatio]

@manics I'd support such switch independent on v1.0.0 or not!

@yuvipanda okay! I'll update this to 0.10.0

Note that we have a v1.0 milestone

[yuvipanda]

Note that we have a v1.0 milestone

Not only that, I wrote a blog post for the Jupyter Blog about v1.0 two years ago https://docs.google.com/document/d/1-DULS3KAm8BO2b5lZ14Tmkq46QI5c8pNRGOwqdX3LcE/edit?usp=sharing. Still haven't published it :D

[yuvipanda]

Thanks, @consideRatio! Will this autotag and push to pypi?

[consideRatio]

@yuvipanda no autotagging or similar, I just followed the steps in RELEASE.md (manually update version, tag, manually update to dev version, push) and that will make a PyPI release be made.

https://github.com/jupyterhub/nbgitpuller/actions/runs/921152283

Done: https://pypi.org/project/nbgitpuller/