packages follow the versions of their corresponding package.
What's the preferred way to ensure they get bumped in lockstep?
E.g. if I bump my resolve and
changes version, my
should mirror that
12/01/2022, 8:23 PM
Ah, you mean third-party published stubs. I was thinking of first-party stubs you write for third-party code
I don't think Pants has any party tricks here. I think it comes down to how you update your top-level
. Maybe group the two together and add a comment to bump both
12/01/2022, 9:38 PM
We end up abusing
to point to normal requirements that are pulled in via
, so that at least all the versions are specified in one place (poetry, which is exported to a
to have fully pinned versions), instead of stubs/plugins in
and main libs in `BUILD`/`requirements.txt` https://github.com/pantsbuild/pants/issues/16044
(That said, this only solves one tiny part of the issue, and not really much about stubs themselves... since the stubs and lib versions might be bumped out of sync and/or end up with different versions in different lockfiles.)