Repository navigation
Add packages to a package set on upload #156
Description
Similar to #154; packages uploaded to the registry should automatically be added to the latest package set, if possible. If the package can't be added to the package set then the registry should issue a warning (but not fail the package upload). Package sets will still need manual curation (ie. a breaking change at the root of a package set will eventually need manual management to update the root package and all its dependents), but this will help keep package sets up to date over time.
To accomplish this, we'll need to:
- Add or update the registry package to the package set that's currently in the default branch of the package sets repository
- Compile the entire package set with its compatible compiler version(s) to verify that the package works with the set
- If successful, commit the updated package set back to the default branch of the package sets repository
Activity
f-f commentedon Dec 1, 2021
Something that we will need to consider is "group updates": sometimes a new version breaks many packages, and the new set will work only if all of these are updated at the same time. Easily solvable by a human, hard to automate?
thomashoneyman commentedon Sep 1, 2022
The spec describes how package sets generation works.
Notably, while we do add a package to the day's set automatically, we ultimately decided not to add the package to the package sets on upload and instead we add the entire day's group at once every day. That's because adding the package to a running set that gets committed once per day brings in some complications:
thomashoneyman commentedon Sep 1, 2022
I'm going to close this because this has been implemented, but we can reopen it or open a separate issue if we want to discuss how we could go about adding packages immediately.