You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This explicit version is used to show that if the version of my monorepo is x.y.z all its packages should be at version x.y.z and they should depend on siblings with x.y.z
The project is bumped from 0.1.1 to 0.1.2 and on reviewing pyproject.toml of monorepo-framework we get something like:
The dependencies are still stuck on 0.1.1. on installation in a project or via pip, version 0.1.2 of monorepo-framework would pull 0.1.1 of monorepo-core and monorepo-utils.
On the other hand if I avoid using explicit version like this:
I run into a case where installing monorepo-framework using pip install monorepo-framework==0.1.1 I would pull monorepo-core==0.1.2, monorepo-utils==0.1.2 if 0.1.2 is released, going against the intended setup.
I wanted to know if targeting sibling dependency versioning schemes was a target of monas and what could be done to support my use case of keeping all packages and their interdependencies on the same version
The text was updated successfully, but these errors were encountered:
Consider the following case of a mono repo:
root
pyproject.toml
Project Structure:
All of these packages are distributable
monorepo-framework
depends onmonorepo-core
andmonorepo-utils
The dependency is added to
monorepo-framework
using the commands:This explicit version is used to show that if the version of my monorepo is
x.y.z
all its packages should be at versionx.y.z
and they should depend on siblings withx.y.z
The project is bumped from
0.1.1
to0.1.2
and on reviewingpyproject.toml
ofmonorepo-framework
we get something like:The dependencies are still stuck on
0.1.1
. on installation in a project or via pip, version0.1.2
ofmonorepo-framework
would pull0.1.1
ofmonorepo-core
andmonorepo-utils
.On the other hand if I avoid using explicit version like this:
I run into a case where installing
monorepo-framework
usingpip install monorepo-framework==0.1.1
I would pullmonorepo-core==0.1.2
,monorepo-utils==0.1.2
if0.1.2
is released, going against the intended setup.I wanted to know if targeting sibling dependency versioning schemes was a target of monas and what could be done to support my use case of keeping all packages and their interdependencies on the same version
The text was updated successfully, but these errors were encountered: