-
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
Release mono-repo requiring sub-package released version #371
Comments
Right now we are releasing the files in alphabetical order. We could inspect the dist files' dependencies and release them in dependent order. |
Yes, but I would still need to make a commit with the sub-package pinning that wouldn't pass the tests, because they would not have been released yet. |
Right, for the commit that updates the versions. I don't see a way around that unless you make a local file that has the next version mapping and the have the version bump use that during release. |
That would work. The release order could also come from this file. |
Interesting idea, a release manifest file. |
Couldn't we just make the python_packages option play that role? Since it's a list, we could respect the order when releasing, and add dependencies.
Means |
Oooh, I like the idea of using that for the order. I'd suggest upgrading to pyproject.toml and adding a general capability to update versions using a manifest file. You can use |
If you want to stick with setuptools, you can use https://github.com/abravalheri/ini2toml |
Thanks, I'll look at that next week, have a great week-end Steve! |
You too! |
Problem
Jupyverse is a Python mono-repo consisting of a "main"
jupyverse
package and a bunch of "sub-packages" in plugins (fps-contents
,fps-kernels
, etc.).When releasing e.g.
0.1.0
, I would likejupyverse
to depend on sub-packages with version==0.1.0
too. But I cannot pin them in setup.cfg, because at the time of release these sub-packages would not have been released yet.Maybe I'm missing something?
The text was updated successfully, but these errors were encountered: