Release review

[ljubon]

Description

create a release workflow based on RELEASING.md
used bumpconfig to update versions

[devstein]

@ljubon This is awesome. Are you able to run this on your fork to show what the output would be for a new release?

[ljubon]

Hi @devstein sorry for the messy history of this PR during rebase i accident matched this branch to master so PR automatically got closed
Let me know what do you thin of my proposal and if it works for your 🤞

[devstein]

This is great!

Before I merge this, can you update the changelog (give yourself a shoutout : )) and the releasing instructions?

[devstein]

@ljubon Would you be interested in becoming a maintainer of sparkmagic?

[ljubon]

This is great!

Before I merge this, can you update the changelog (give yourself a shoutout : )) and the releasing instructions?

Got it, bot RELEASE.md and CHANGELOG.md are updated 👍

[ljubon]

@ljubon Would you be interested in becoming a maintainer of sparkmagic?

I would be honored to become a maintainer and help the community grow 🙏

[devstein]

I would be honored to become a maintainer and help the community grow 🙏

Amazing! sparkmagic is widely use and we need the additional support

[devstein]

@ljubon I granted you write access 🚀 Let me know if you run into issues or have questions.

One of the low-effort, but higher priority tasks on the backlog is #811

In general, dependencies are relatively safe to bump. The dependencies that require significant scrutiny and testing is anything related to Jupyer (ipykernel, ipython, ipywidgets, jupyter-server, etc)