-
Notifications
You must be signed in to change notification settings - Fork 66
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
Support package release dependencies in multi-Python packages #372
base: main
Are you sure you want to change the base?
Conversation
Yeah, I finally figured out how to test local changes in #363. Perhaps we should wait for that before doing this? |
Sounds good. In the meantime, I can always achieve what this PR does in two steps:
|
Okay, you can rebase now that #363 is merged. |
509a7d2
to
2651a46
Compare
Codecov Report
@@ Coverage Diff @@
## main #372 +/- ##
==========================================
- Coverage 82.93% 82.60% -0.33%
==========================================
Files 21 21
Lines 2866 2898 +32
Branches 374 382 +8
==========================================
+ Hits 2377 2394 +17
- Misses 356 368 +12
- Partials 133 136 +3
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
I rebased an tried to release jupyverse with this branch, but it failed in
Any idea? |
Ah, I see that we need to store the RH_REF in the metadata file and use that. |
2651a46
to
15dc994
Compare
15dc994
to
89499ad
Compare
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 |
89499ad
to
2141efd
Compare
Still fails:
|
I don't think this is related to the error from David above. When trying to release JupyterLab, the draft PR got converted and populated with all to-be-published assets see draft release. But the publication failed because the |
For now you can create a tag for 519b8dd 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. |
I'm not sure, because there is the same issue in the "Check Release" action of this PR. |
@davidbrochart I'd recommend switching away from |
1b6ef17
to
58ae52a
Compare
This PR now fails at check-python:
Here |
If I do so it fails at extract-release:
|
58ae52a
to
39c3044
Compare
@blink1073 this still fails. Any idea what can be done? |
You'd have to publish the packages to the local pypi server before calling check-python, and then make sure you are running the local pypi server during check-python, or skip check-python. |
The releaser has a utility function to start the local PyPI server: jupyter_releaser/jupyter_releaser/python.py Lines 183 to 196 in a4de95e
There doesn't seem to be a way to stop it though. So not sure if starting it before |
Closes #371.
This fails with
check-python
,extract-release
... because the dependent packages have not been released on PyPI yet.Maybe there is a way to add the just-created (local) releases in the package providers?