Steven Silvester

Hi @danyrouh, you can avoid building the python dist files by skipping the `build-python` step. ``` [tool.jupyter-releaser] skip = ["build-python"] ````

Yeah, I finally figured out how to test local changes in #363. Perhaps we should wait for that before doing this?

Okay, you can rebase now that #363 is merged.

Ah, I see that we need to store the RH_REF in the metadata file and use that.

https://github.com/jupyter-server/jupyter_releaser/pull/375

I think it is because the original draft release was over one day old and got pruned. You'll have to start over.

Oh, I see it is still there. Maybe try with the full url: https://github.com/jupyter-server/jupyverse/releases/tag/untagged-43adf70df0043151e18b

For now you can create a tag for https://github.com/jupyter-server/jupyter_releaser/commit/519b8dd8dd60b2e88c199f9a1dfba6a6c0ab2457 on your fork, and select that tag when running your workflows, you can get unblocked.

@davidbrochart I think the error you are seeing is from the multi-dependency handling.

@davidbrochart I'd recommend switching away from `tbump` in general. See https://github.com/jupyter-server/jupyter_releaser/pull/374 for an example of how to switch to `hatchling version` instead.