-
Notifications
You must be signed in to change notification settings - Fork 4
Grouped package releases #103
Copy link
Copy link
Open
Labels
RFCProposed feature or change - open for feedbackProposed feature or change - open for feedbackcrt:sampoChanges in Sampo CLI crate.Changes in Sampo CLI crate.crt:sampo-coreChanges in Sampo core logic or internal utils.Changes in Sampo core logic or internal utils.crt:sampo-github-actionChanges in Sampo's Github action crate.Changes in Sampo's Github action crate.
Description
Metadata
Metadata
Assignees
Labels
RFCProposed feature or change - open for feedbackProposed feature or change - open for feedbackcrt:sampoChanges in Sampo CLI crate.Changes in Sampo CLI crate.crt:sampo-coreChanges in Sampo core logic or internal utils.Changes in Sampo core logic or internal utils.crt:sampo-github-actionChanges in Sampo's Github action crate.Changes in Sampo's Github action crate.
Describe the problem
Currently, all packages in a workspace are released together in a single PR. There is no way to release subsets of packages independently when different packages have different release cadences or stability requirements (except using multiple branches).
What's the expected result?
Add « release groups » in
.sampo/config.tomlto release packages separately. With named collections of packages with independent release workflows. Packages in one group cannot depend on packages in another group, and ungrouped packages can be depended on by any group.In
sampoCLI, we should be able to target specific groups for release/publish, both via--group <name>flag or in CLI UI. Insampo-github-action, it should create separate PRs per group.Example use case: separate experimental packages from stable core, or isolate high-frequency released packages from low-frequency ones.