-
-
Notifications
You must be signed in to change notification settings - Fork 27
Open
Description
In several repositories we are splitting into multiple modules with completely decoupled release versioning.
- fundamental constants and providers into a distinct module what will rev only occasionally. It may be at version 1.x forever
- tools and contrib which may update every month. version 2.x of those may still depend on older ones
So we need a bcr workflow that takes a module and version string as input. Alternate is to think of the tag as package-version, but then we need a way to map back from canonical name of the packge to the submodule folder it is in, so easier to just take the module path as input.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels